All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: Zhenguo Yao <yaozhenguo1@gmail.com>
Cc: mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
	corbet@lwn.net, Mike Rapoport <rppt@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	yaozhenguo@jd.com, Matthew Wilcox <willy@infradead.org>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v7] hugetlbfs: Extend the definition of hugepages parameter to support node allocation
Date: Mon, 4 Oct 2021 10:34:49 -0700	[thread overview]
Message-ID: <669bd927-397e-f2d8-3be4-798b9d7c4e8d@oracle.com> (raw)
In-Reply-To: <CA+WzAR=eVOYamSoEyuphiL89qXh+=0kBZAPkxAnuqamMWgrTSQ@mail.gmail.com>

On 10/4/21 8:06 AM, Zhenguo Yao wrote:
> Hi Mike:
> 
> Thanks for your review. I notice that this patch has already been in
> linux-next. Do I need to submit another version of this patch or
> provide a new patch to fix the problems  you pointed out?

This change goes through Andrew Morton's tree, and he will decide how to
update.

My suggestion is to send a new version with suggested updates as well as
my 'Reviewed-by:".

Thanks,
-- 
Mike Kravetz

      reply	other threads:[~2021-10-04 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 10:41 [PATCH v7] hugetlbfs: Extend the definition of hugepages parameter to support node allocation Zhenguo Yao
2021-09-28 16:47 ` Mike Rapoport
2021-09-29  5:38   ` Zhenguo Yao
2021-09-29  5:38     ` Zhenguo Yao
2021-09-29 19:24 ` Nathan Chancellor
2021-09-29 22:27   ` Mike Rapoport
2021-09-29 23:25     ` Andrew Morton
2021-10-01 22:33 ` Mike Kravetz
2021-10-04 15:06   ` Zhenguo Yao
2021-10-04 15:06     ` Zhenguo Yao
2021-10-04 17:34     ` Mike Kravetz [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=669bd927-397e-f2d8-3be4-798b9d7c4e8d@oracle.com \
    --to=mike.kravetz@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=rppt@kernel.org \
    --cc=willy@infradead.org \
    --cc=yaozhenguo1@gmail.com \
    --cc=yaozhenguo@jd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.