All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brendan Jackman" <brendan.jackman@linux.dev>
To: <sashiko-reviews@lists.linux.dev>,
	"Brendan Jackman" <jackmanb@google.com>
Cc: <linux-rt-devel@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 07/18] mm: move some stuff to mm/page_alloc.h
Date: Fri, 03 Jul 2026 09:25:56 +0000	[thread overview]
Message-ID: <DJOTTXFDIIN3.3JGPUL349UM63@linux.dev> (raw)
In-Reply-To: <20260702102828.3C8651F000E9@smtp.kernel.org>

On Thu Jul 2, 2026 at 10:28 AM UTC, sashiko-bot wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Duplicate declaration of `drain_local_pages()` in `mm/page_alloc.h` contradicts the commit message.
> --
>
> commit 54f4dc2300a55c6c9cef3e3916ba57e09ad07e39
> Author: Brendan Jackman <jackmanb@google.com>
>
> mm: move some stuff to mm/page_alloc.h
>
> This commit shrinks the scope of several internal functions by moving their
> declarations from the public include/linux/gfp.h header to the internal
> mm/page_alloc.h header.
>
>> diff --git a/mm/page_alloc.h b/mm/page_alloc.h
>> index a4f4b325381ad..6bb50bae3ba27 100644
>> --- a/mm/page_alloc.h
>> +++ b/mm/page_alloc.h
>
> [ ... ]
>
>> @@ -266,6 +266,34 @@ static inline bool free_area_empty(struct free_area *area, int migratetype)
>>  	return list_empty(&area->free_list[migratetype]);
>>  }
>>  
>> +/* Convert GFP flags to their corresponding migrate type */
>> +#define GFP_MOVABLE_MASK (__GFP_RECLAIMABLE|__GFP_MOVABLE)
>
> [ ... ]
>
>> +bool decay_pcp_high(struct zone *zone, struct per_cpu_pages *pcp);
>> +void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
>> +void drain_all_pages(struct zone *zone);
>> +void drain_local_pages(struct zone *zone);
>
> [Severity: Low]
> The commit message notes that drain_local_pages() is still used externally
> and needs to stay behind in include/linux/gfp.h. Since it was successfully
> left in the public header, is this declaration in mm/page_alloc.h an
> accidental duplicate?

Ugh, yep. My local Sashiko run found this but apparently I failed to
actually fix it...? Doing thigs is so hard.

  reply	other threads:[~2026-07-03  9:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  9:49 [PATCH v4 00/18] mm: Some cleanups for page allocator APIs Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 01/18] mm/page_alloc: rename ALLOC_TRYLOCK -> ALLOC_NOLOCK Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 02/18] mm/page_alloc: some renames to clarify alloc_flags scopes Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 03/18] mm: name some args in a function declaration Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 04/18] mm: Split out internal page_alloc.h Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 05/18] mm/page_alloc: unify __alloc_frozen_pages[_nolock]_noprof() Brendan Jackman
2026-07-03  9:20   ` Vlastimil Babka (SUSE)
2026-07-02  9:49 ` [PATCH v4 06/18] mm/page_alloc: relax GFP WARN in nolock allocs Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 07/18] mm: move some stuff to mm/page_alloc.h Brendan Jackman
2026-07-02 10:28   ` sashiko-bot
2026-07-03  9:25     ` Brendan Jackman [this message]
2026-07-02  9:49 ` [PATCH v4 08/18] perf/x86/intel: Use higher-level allocator API Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 09/18] KVM: VMX: " Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 10/18] x86/virt: " Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 11/18] sgi-xp: " Brendan Jackman
2026-07-02 10:54   ` sashiko-bot
2026-07-02  9:49 ` [PATCH v4 12/18] net/funeth: Switch to " Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 13/18] mm: Remove __alloc_pages_node() Brendan Jackman
2026-07-02 11:11   ` sashiko-bot
2026-07-02  9:49 ` [PATCH v4 14/18] mm: Move __alloc_pages() to mm/page_alloc.h Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 15/18] mm: replace __GFP_NO_CODETAG with ALLOC_NO_CODETAG Brendan Jackman
2026-07-03  2:29   ` Hao Ge
2026-07-03  9:24   ` Vlastimil Babka (SUSE)
2026-07-02  9:49 ` [PATCH v4 16/18] mm: remove the __GFP_NO_OBJ_EXT flag Brendan Jackman
2026-07-02  9:49 ` [PATCH v4 17/18] mm/page_alloc: drop alloc_flags arg from alloc_flags_cma() Brendan Jackman
2026-07-03  9:28   ` Vlastimil Babka (SUSE)
2026-07-02  9:49 ` [PATCH v4 18/18] mm: factor out can_spin_trylock() Brendan Jackman
2026-07-02 12:28   ` sashiko-bot
2026-07-03  9:16     ` Brendan Jackman
2026-07-03  9:32   ` Vlastimil Babka (SUSE)
2026-07-03 11:43     ` Brendan Jackman
2026-07-03  9:38   ` Harry Yoo

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=DJOTTXFDIIN3.3JGPUL349UM63@linux.dev \
    --to=brendan.jackman@linux.dev \
    --cc=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.