From: zhiguojiang <justinjiang@vivo.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
opensource.kernel@vivo.com
Subject: Re: [PATCH v2] mm: ALLOC_HIGHATOMIC flag allocation issue
Date: Wed, 22 Nov 2023 09:43:38 +0800 [thread overview]
Message-ID: <dbab7bb0-e40b-4642-9fe0-c1cbb7263f1c@vivo.com> (raw)
In-Reply-To: <ZVzTThaEgDcbvtM9@casper.infradead.org>
在 2023/11/21 23:57, Matthew Wilcox 写道:
> On Tue, Nov 21, 2023 at 03:51:29PM +0800, Zhiguo Jiang wrote:
>> Update comments and modify variable highatomic_allocation to highatomic.
> You sent the patch relative to your last patch again.
> You have to send the patch relative to Linus' tree or Andrew's tree.
Why command "git pull --rebase=merges " can't get latest code?
I have update in patch v3.
Thanks
prev parent reply other threads:[~2023-11-22 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231121075129.1530-1-justinjiang@vivo.com>
2023-11-21 15:57 ` Matthew Wilcox
2023-11-22 1:43 ` zhiguojiang [this message]
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=dbab7bb0-e40b-4642-9fe0-c1cbb7263f1c@vivo.com \
--to=justinjiang@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=opensource.kernel@vivo.com \
--cc=willy@infradead.org \
/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