From: Anshuman Khandual <anshuman.khandual@arm.com>
To: marc.herbert@linux.intel.com
Cc: Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: move hugetlb_sysctl_init() to the __init section
Date: Wed, 19 Mar 2025 11:57:49 +0530 [thread overview]
Message-ID: <c03fbda6-4465-4ada-a9eb-d02893f509d4@arm.com> (raw)
In-Reply-To: <20250319060041.2737320-1-marc.herbert@linux.intel.com>
On 3/19/25 11:30, marc.herbert@linux.intel.com wrote:
> From: Marc Herbert <Marc.Herbert@linux.intel.com>
>
> hugetlb_sysctl_init() is only invoked once by an __init function and is
> merely a wrapper around another __init function so there is not reason
> to keep it.
>
> Fixes the following warning when toning down some GCC inline options:
>
> WARNING: modpost: vmlinux: section mismatch in reference:
> hugetlb_sysctl_init+0x1b (section: .text) ->
> __register_sysctl_init (section: .init.text)
>
> Signed-off-by: Marc Herbert <Marc.Herbert@linux.intel.com>
> ---
> mm/hugetlb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 65068671e460..a2850b26aed9 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -4900,7 +4900,7 @@ static const struct ctl_table hugetlb_table[] = {
> },
> };
>
> -static void hugetlb_sysctl_init(void)
> +static void __init hugetlb_sysctl_init(void)
> {
> register_sysctl_init("vm", hugetlb_table);
> }
LGTM
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
next prev parent reply other threads:[~2025-03-19 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 6:00 marc.herbert
2025-03-19 6:27 ` Anshuman Khandual [this message]
2025-03-19 7:22 ` Andrew Morton
2025-03-20 17:31 ` Marc Herbert
2025-03-19 7:44 ` Muchun Song
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=c03fbda6-4465-4ada-a9eb-d02893f509d4@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marc.herbert@linux.intel.com \
--cc=muchun.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox