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: Mon, 12 Jan 2026 16:33:42 +0000 [thread overview]
Message-ID: <49229782-acf5-4e33-b317-63399deb6f6d@lucifer.local> (raw)
In-Reply-To: <20260112161820.604669-1-ben.dooks@codethink.co.uk>
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).
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> ---
> mm/khugepaged.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 97d1b2824386..c9bd0df632bd 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -826,7 +826,7 @@ static void khugepaged_alloc_sleep(void)
> remove_wait_queue(&khugepaged_wait, &wait);
> }
>
> -struct collapse_control khugepaged_collapse_control = {
> +static struct collapse_control khugepaged_collapse_control = {
> .is_khugepaged = true,
> };
>
> --
> 2.37.2.352.g3c44437643
>
Cheers, Lorenzo
next prev parent reply other threads:[~2026-01-12 16:34 UTC|newest]
Thread overview: 4+ 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 [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=49229782-acf5-4e33-b317-63399deb6f6d@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