[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZVF9h6M6dK5AZDg7@casper.infradead.org>
Date: Mon, 13 Nov 2023 01:36:07 +0000
From: Matthew Wilcox <willy@...radead.org>
To: zhiguojiang <justinjiang@...o.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
opensource.kernel@...o.com
Subject: Re: [PATCH v2 1/1] mm: ALLOC_HIGHATOMIC flag allocation issue
On Mon, Nov 13, 2023 at 09:04:49AM +0800, zhiguojiang wrote:
>
>
> 在 2023/11/11 14:25, Matthew Wilcox 写道:
> > On Thu, Nov 09, 2023 at 09:49:54AM -0800, Andrew Morton wrote:
> > > On Thu, 9 Nov 2023 15:31:33 +0800 Zhiguo Jiang <justinjiang@...o.com> wrote:
> > >
> > > > Add a new bool* argument to pass return flag instead of *alloc_flags
> > > > and add the related comments.
> > > Please retain (and update) the changelog with each version of a patch.
> > >
> > > For reviewers (please), here's the v1 changelog:
> > This patch isn't diffed against the current tree. It can't be reviewed.
> patch v1:
> https://lore.kernel.org/all/20231108065408.1861-1-justinjiang@vivo.com/
> patch v2:
> https://lore.kernel.org/all/20231109073133.792-2-justinjiang@vivo.com/
> patch v3:
> https://lore.kernel.org/all/20231110020840.1031-1-justinjiang@vivo.com/
None of those are diffed against the current tree. You need to send a
patch that applies cleanly to either linux-next or current Linus head.
Not a patch on top of an earlier version of your patch.
Powered by blists - more mailing lists