linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	kernel test robot <lkp@intel.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: WARNING: modpost: vmlinux: section mismatch in reference: mm_cmdline_setup+0x94 (section: .text.unlikely) -> memblock (section: .init.data)
Date: Fri, 28 Mar 2025 00:55:42 +0000	[thread overview]
Message-ID: <20250328005542.q7oumy7v2bvpuyyd@master> (raw)
In-Reply-To: <20250327123624.bd59f1307d5c5b29b1b9ac08@linux-foundation.org>

On Thu, Mar 27, 2025 at 12:36:24PM -0700, Andrew Morton wrote:
>On Thu, 27 Mar 2025 01:13:12 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:
>
>> Since it is only used by mmu_init() which is annotated by __init, I think the
>> proper way is to add __init to mm_cmdline_setup.
>> 
>> 
>> diff --git a/arch/microblaze/mm/init.c b/arch/microblaze/mm/init.c
>> index 4520c5741579..e98cfaf1c62b 100644
>> --- a/arch/microblaze/mm/init.c
>> +++ b/arch/microblaze/mm/init.c
>> @@ -143,7 +143,7 @@ int page_is_ram(unsigned long pfn)
>>  /*
>>   * Check for command-line options that affect what MMU_init will do.
>>   */
>> -static void mm_cmdline_setup(void)
>> +static void __init mm_cmdline_setup(void)
>>  {
>>  	unsigned long maxmem = 0;
>>  	char *p = cmd_line;
>
>That's a correct change anyway.  Please send along a patch sometime?

Sure.

-- 
Wei Yang
Help you, Help me


      reply	other threads:[~2025-03-28  0:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  4:59 kernel test robot
2025-03-27  1:13 ` Wei Yang
2025-03-27 19:36   ` Andrew Morton
2025-03-28  0:55     ` Wei Yang [this message]

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=20250328005542.q7oumy7v2bvpuyyd@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox