From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
To: Kent Gibson <warthog618@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: WARNING: modpost: vmlinux: section mismatch in reference: ip_md_tunnel_xmit+0x9e (section: .text) -> .LBB102 (section: .init.text)
Date: Sat, 27 Apr 2024 10:21:20 +0200 [thread overview]
Message-ID: <CACMJSetLpWn5H+Dk9kip5oVu5gG8fKB=PPHDRz901-JeUV1LcQ@mail.gmail.com> (raw)
In-Reply-To: <20240427004819.GA24436@rigel>
On Sat, 27 Apr 2024 at 02:48, Kent Gibson <warthog618@gmail.com> wrote:
>
> On Sat, Apr 27, 2024 at 05:29:42AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 3022bf37da50ce0ee3ba443ec5f86fa8c28aacd0
> > commit: 83092341e15d0dfee1caa8dc502f66c815ccd78a gpio: cdev: fix missed label sanitizing in debounce_setup()
> > date: 3 weeks ago
> > config: riscv-randconfig-r021-20230409 (https://download.01.org/0day-ci/archive/20240427/202404270534.8VgyE2XE-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/20240427/202404270534.8VgyE2XE-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/202404270534.8VgyE2XE-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> >
>
> Bart,
>
> does this make any sense to you, cos I'm not seeing any connection
> between that commit and these warnings?
>
> Cheers,
> Kent.
>
I think this is a false positive.
Bart
next prev parent reply other threads:[~2024-04-27 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 21:29 WARNING: modpost: vmlinux: section mismatch in reference: ip_md_tunnel_xmit+0x9e (section: .text) -> .LBB102 (section: .init.text) kernel test robot
2024-04-27 0:48 ` Kent Gibson
2024-04-27 8:21 ` Bartosz Golaszewski [this message]
2024-04-30 13:12 ` Philip Li
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='CACMJSetLpWn5H+Dk9kip5oVu5gG8fKB=PPHDRz901-JeUV1LcQ@mail.gmail.com' \
--to=bartosz.golaszewski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=warthog618@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).