linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: "Xu, Yanfei" <yanfei.xu@windriver.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/page_alloc: correct return value when failing at preparing
Date: Tue, 13 Jul 2021 13:14:08 +0100	[thread overview]
Message-ID: <20210713121408.GC3809@techsingularity.net> (raw)
In-Reply-To: <98c83852-6745-bf57-2415-696edea89704@windriver.com>

On Sat, Jul 10, 2021 at 02:58:02PM +0800, Xu, Yanfei wrote:
> 
> 
> On 7/9/21 8:22 PM, Mel Gorman wrote:
> > [Please note: This e-mail is from an EXTERNAL e-mail address]
> > 
> > On Fri, Jul 09, 2021 at 06:28:54PM +0800, Yanfei Xu wrote:
> > > If the array passed in is already partially populated, we should
> > > return "nr_populated" even failing at preparing arguments stage.
> > > 
> > > Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
> > 
> > ff4b2b4014cb ("mm/page_alloc: correct return value of populated elements if bulk array is populated")
> > 
> 
> This is a different return location from you posted.
> 

You're right, I'll pick this up and stage it with a series of patches
that should have gone in during the merge window but were too late.

Thanks.

-- 
Mel Gorman
SUSE Labs


      reply	other threads:[~2021-07-13 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 10:28 Yanfei Xu
2021-07-09 10:28 ` [PATCH 2/2] mm/page_alloc: avoid counting event if no successful allocation Yanfei Xu
2021-07-09 12:26   ` Mel Gorman
2021-07-10 11:31     ` Xu, Yanfei
2021-07-09 12:22 ` [PATCH 1/2] mm/page_alloc: correct return value when failing at preparing Mel Gorman
2021-07-10  6:58   ` Xu, Yanfei
2021-07-13 12:14     ` Mel Gorman [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=20210713121408.GC3809@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yanfei.xu@windriver.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