All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Hari Bathini <hbathini@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree
Date: Thu, 16 May 2024 12:42:01 +1000	[thread overview]
Message-ID: <87cypmwk92.fsf@mail.lhotse> (raw)
In-Reply-To: <20240515163708.3380c4d1@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging the powerpc tree, today's (it may have been yesterday's)
> linux-next build (powerpc allyesconfig) produced this warning:
>
> WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text)

I don't see the warning, but clearly it is possible if the compiler
decides not to inline fadump_setup_param_area().

What compiler version are you using?

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: linux-next: build warning after merge of the powerpc tree
Date: Thu, 16 May 2024 12:42:01 +1000	[thread overview]
Message-ID: <87cypmwk92.fsf@mail.lhotse> (raw)
In-Reply-To: <20240515163708.3380c4d1@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging the powerpc tree, today's (it may have been yesterday's)
> linux-next build (powerpc allyesconfig) produced this warning:
>
> WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text)

I don't see the warning, but clearly it is possible if the compiler
decides not to inline fadump_setup_param_area().

What compiler version are you using?

cheers

  reply	other threads:[~2024-05-16  2:42 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  6:37 linux-next: build warning after merge of the powerpc tree Stephen Rothwell
2024-05-15  6:37 ` Stephen Rothwell
2024-05-16  2:42 ` Michael Ellerman [this message]
2024-05-16  2:42   ` Michael Ellerman
2024-05-16  4:36   ` Stephen Rothwell
2024-05-16  4:36     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2025-05-13 10:28 Stephen Rothwell
2025-05-29 23:44 ` Stephen Rothwell
2025-05-30 13:10   ` Athira Rajeev
2025-04-29  8:57 Stephen Rothwell
2025-04-29  8:17 Stephen Rothwell
2025-02-19  4:46 Stephen Rothwell
2025-02-19  5:23 ` Madhavan Srinivasan
2025-02-19  5:49 ` Andrew Donnellan
2024-11-20  6:13 Stephen Rothwell
2023-02-16  3:40 Stephen Rothwell
2023-02-16  3:40 ` Stephen Rothwell
2023-02-16 18:06 ` Josh Poimboeuf
2023-02-16 18:06   ` Josh Poimboeuf
2023-02-17  1:35   ` Michael Ellerman
2023-02-17  7:05     ` Josh Poimboeuf
2023-02-17  7:05       ` Josh Poimboeuf
2021-08-23  9:55 Stephen Rothwell
2021-08-23  9:55 ` Stephen Rothwell
2021-08-23 10:48 ` Stephen Rothwell
2021-08-23 10:48   ` Stephen Rothwell
2021-08-23 14:19   ` Jonathan Corbet
2021-08-23 14:19     ` Jonathan Corbet
2021-08-23 23:21     ` Stephen Rothwell
2021-08-23 23:21       ` Stephen Rothwell
2021-08-24  5:18   ` Aneesh Kumar K.V
2021-08-24  5:18     ` Aneesh Kumar K.V
2021-08-24 13:46     ` Jonathan Corbet
2021-08-24 13:46       ` Jonathan Corbet
2021-04-15  8:52 Stephen Rothwell
2021-04-15  8:52 ` Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2021-04-16 10:54   ` Michael Ellerman
2021-04-14 23:36 Stephen Rothwell
2021-04-14 23:36 ` Stephen Rothwell
2019-11-13 22:34 Stephen Rothwell
2019-11-13 22:34 ` Stephen Rothwell
2017-09-04  8:53 Stephen Rothwell
2017-09-04  8:59 ` Cédric Le Goater
2015-10-20  5:21 Stephen Rothwell
2015-10-20  5:21 ` Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45   ` Stephen Rothwell
2011-05-19  3:19 Stephen Rothwell
2011-05-19  3:19 ` Stephen Rothwell

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=87cypmwk92.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=hbathini@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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.