From: Philip Li <philip.li@intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: [linux-next:master 10192/10451] WARNING: modpost: vmlinux: section mismatch in reference: mgmt_index_removed+0x24 (section: .text) -> .LBB3864 (section: .init.text)
Date: Thu, 11 Jul 2024 10:25:59 +0800 [thread overview]
Message-ID: <Zo9Ct9nUT7/nHna6@rli9-mobl> (raw)
In-Reply-To: <CACMJSesFR4L4wYFDX0xJKGqfZ80vq0HG3J+7Y1kWqodjqTS_Vw@mail.gmail.com>
On Mon, Jul 08, 2024 at 08:51:53PM +0200, Bartosz Golaszewski wrote:
> On Mon, 8 Jul 2024 at 18:15, kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 0b58e108042b0ed28a71cd7edf5175999955b233
> > commit: d009853d746532353e0d1517c75289bb7dbf0450 [10192/10451] Merge branch 'gpio/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git
> > config: riscv-randconfig-r033-20230517 (https://download.01.org/0day-ci/archive/20240709/202407090029.a72M25wz-lkp@intel.com/config)
> > compiler: riscv32-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240709/202407090029.a72M25wz-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202407090029.a72M25wz-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> >
>
> While I can confirm this can be reproduced easily, I am not sure if
> this has anything to do with GPIO? Looks like it's an unrelated issue.
Sorry for this false positive. It is a wrong report which seems to only occur on
riscv arch. The bot will be fixed to avoid sending this kind of issues.
Sorry for the trouble.
>
> Bart
>
prev parent reply other threads:[~2024-07-11 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202407090029.a72M25wz-lkp@intel.com>
2024-07-08 18:51 ` Bartosz Golaszewski
2024-07-11 2:25 ` Philip Li [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=Zo9Ct9nUT7/nHna6@rli9-mobl \
--to=philip.li@intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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