public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Michael Ellerman <mpe@ellerman•id.au>,
	PowerPC <linuxppc-dev@lists•ozlabs.org>
Cc: Sourabh Jain <sourabhjain@linux•ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the powerpc tree
Date: Tue, 24 Oct 2023 17:38:43 +1100	[thread overview]
Message-ID: <20231024173843.07ca9afc@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warnings:

WARNING: modpost: vmlinux: section mismatch in reference: process_fadump+0x2c8 (section: .text.process_fadump) -> fadump_setup_elfcorehdr_buf (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: process_fadump+0x2f4 (section: .text.process_fadump) -> fadump_populate_elfcorehdr (section: .init.text)

Probably introduced by commit

  c17687d0d62d ("powerpc: make fadump resilient with memory add/remove events")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-10-24  6:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  6:38 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-27 12:00 linux-next: build warnings after merge of the powerpc tree 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=20231024173843.07ca9afc@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=sourabhjain@linux$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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