From: Dan Streetman <ddstreet@ieee.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Linux-MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH 0/2] z3fold fixes
Date: Tue, 29 Nov 2016 17:33:19 -0500 [thread overview]
Message-ID: <CALZtONCzseKs22189B3b+TEPKu8JPQ4WcGGB0zPj4KNuKiUAig@mail.gmail.com> (raw)
In-Reply-To: <20161126201534.5d5e338f678b478e7a7b8dc3@gmail.com>
On Sat, Nov 26, 2016 at 2:15 PM, Vitaly Wool <vitalywool@gmail.com> wrote:
> Here come 2 patches with z3fold fixes for chunks counting and locking. As commit 50a50d2 ("z3fold: don't fail kernel build is z3fold_header is too big") was NAK'ed [1], I would suggest that we removed that one and the next z3fold commit cc1e9c8 ("z3fold: discourage use of pages that weren't compacted") and applied the coming 2 instead.
Instead of adding these onto all the previous ones, could you redo the
entire z3fold series? I think it'll be simpler to review the series
all at once and that would remove some of the stuff from previous
patches that shouldn't be there.
If that's ok with Andrew, of course, but I don't think any of the
z3fold patches have been pushed to Linus yet.
>
> Signed-off-by: Vitaly Wool <vitalywool@gmail.com>
>
> [1] https://lkml.org/lkml/2016/11/25/595
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-11-29 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 19:15 Vitaly Wool
2016-11-26 19:17 ` [PATCH 1/2] z3fold: fix header size related issues Vitaly Wool
2016-11-26 19:21 ` [PATCH 2/2] z3fold: fix locking issues Vitaly Wool
2016-11-29 22:33 ` Dan Streetman [this message]
2016-11-29 22:39 ` [PATCH 0/2] z3fold fixes Andrew Morton
2016-12-18 8:15 ` Vitaly Wool
2016-12-22 21:55 ` Dan Streetman
2016-12-22 23:04 ` Vitaly Wool
2016-12-23 13:09 ` Dan Streetman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALZtONCzseKs22189B3b+TEPKu8JPQ4WcGGB0zPj4KNuKiUAig@mail.gmail.com \
--to=ddstreet@ieee.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vitalywool@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox