From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, david@kernel.org
Subject: Re: [PATCH] mm/khugepaged: make khugepaged_collapse_control static
Date: Tue, 13 Jan 2026 09:50:57 +0000 [thread overview]
Message-ID: <80157a8e-eee3-4e03-8319-990c3d4b784c@lucifer.local> (raw)
In-Reply-To: <2a289c18-b5b7-497c-bd6d-a25602706b23@codethink.co.uk>
On Tue, Jan 13, 2026 at 09:26:37AM +0000, Ben Dooks wrote:
> On 12/01/2026 16:33, Lorenzo Stoakes wrote:
> > On Mon, Jan 12, 2026 at 04:18:20PM +0000, Ben Dooks wrote:
> > > Make khugepaged_collapse_control as it is not exported.
> > > Fixes the following sparse warning:
> > >
> > > mm/khugepaged.c:829:25: warning: symbol 'khugepaged_collapse_control' was not declared. Should it be static?
> >
> > Thanks for the patch, but sorry to say that this has already been addressed in
> > [0].
> >
> > [0]: https://lore.kernel.org/all/20251224111351.41042-14-shivankg@amd.com/
> >
> > >
> > > Fixes: 34d6b470ab9cf ("mm/khugepaged: add struct collapse_control")
> >
> > (Small note: for something like this that isn't fixing an actual bug we don't
> > use a fixes like this).
>
> Is this a subsystem preference because I was told I needed it for other
> patches.
It's kernel-wide see [0].
If that's not clear, really you only want to do that if a bug
(i.e. something has runtime impact that breaks something) exists in a
released kernel that you are resolving.
It's to help us keep track of when bugs appeared and when they were
resolved, most pertinent to stable backports (if you fixed an actual bug
you'd typically want to Cc stable to kick off a backport).
[0]: https://docs.kernel.org/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
>
> --
> Ben Dooks http://www.codethink.co.uk/
> Senior Engineer Codethink - Providing Genius
>
> https://www.codethink.co.uk/privacy.html
Thanks, Lorenzo
next prev parent reply other threads:[~2026-01-13 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 16:18 Ben Dooks
2026-01-12 16:22 ` Ben Dooks
2026-01-12 16:33 ` Lorenzo Stoakes
2026-01-13 9:26 ` Ben Dooks
2026-01-13 9:50 ` Lorenzo Stoakes [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 16:18 Ben Dooks
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=80157a8e-eee3-4e03-8319-990c3d4b784c@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ben.dooks@codethink.co.uk \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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