From: Michal Hocko <mhocko@kernel.org>
To: Huaisheng Ye <yehs1@lenovo.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, vbabka@suse.cz,
mgorman@techsingularity.net, pasha.tatashin@oracle.com,
hannes@cmpxchg.org, penguin-kernel@I-love.SAKURA.ne.jp,
colyli@suse.de, chengnt@lenovo.com
Subject: Re: [PATCH] mm/page_alloc: Remove useless parameter of finalise_ac
Date: Thu, 3 May 2018 09:51:11 +0200 [thread overview]
Message-ID: <20180503075111.GB4535@dhcp22.suse.cz> (raw)
In-Reply-To: <1525318929-91048-1-git-send-email-yehs1@lenovo.com>
On Thu 03-05-18 11:42:09, Huaisheng Ye wrote:
> finalise_ac has parameter order which is not used at all.
> Remove it.
>
> Signed-off-by: Huaisheng Ye <yehs1@lenovo.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> mm/page_alloc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 905db9d..291e194 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -4326,8 +4326,7 @@ static inline bool prepare_alloc_pages(gfp_t gfp_mask, unsigned int order,
> }
>
> /* Determine whether to spread dirty pages and what the first usable zone */
> -static inline void finalise_ac(gfp_t gfp_mask,
> - unsigned int order, struct alloc_context *ac)
> +static inline void finalise_ac(gfp_t gfp_mask, struct alloc_context *ac)
> {
> /* Dirty zone balancing only done in the fast path */
> ac->spread_dirty_pages = (gfp_mask & __GFP_WRITE);
> @@ -4358,7 +4357,7 @@ struct page *
> if (!prepare_alloc_pages(gfp_mask, order, preferred_nid, nodemask, &ac, &alloc_mask, &alloc_flags))
> return NULL;
>
> - finalise_ac(gfp_mask, order, &ac);
> + finalise_ac(gfp_mask, &ac);
>
> /* First allocation attempt */
> page = get_page_from_freelist(alloc_mask, order, alloc_flags, &ac);
> --
> 1.8.3.1
>
--
Michal Hocko
SUSE Labs
parent reply other threads:[~2018-05-03 7:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1525318929-91048-1-git-send-email-yehs1@lenovo.com>]
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=20180503075111.GB4535@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengnt@lenovo.com \
--cc=colyli@suse.de \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=pasha.tatashin@oracle.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=vbabka@suse.cz \
--cc=yehs1@lenovo.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