All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
	<oe-kbuild-all@lists.linux.dev>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [linux-next:master 9094/10451] WARNING: modpost: vmlinux: section mismatch in reference: remove_device+0x4e (section: .text) -> .L604 (section: .init.text)
Date: Thu, 11 Jul 2024 10:24:24 +0800	[thread overview]
Message-ID: <Zo9CWFsJWComLMjK@rli9-mobl> (raw)
In-Reply-To: <6c6b2f14-9034-44c0-9ac2-81365086a788@redhat.com>

On Wed, Jul 10, 2024 at 05:03:28AM +0200, David Hildenbrand wrote:
> On 09.07.24 23:55, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   82d01fe6ee52086035b201cfa1410a3b04384257
> > commit: cbdfb23849b330b0156760ee0d73348e020b8cdd [9094/10451] mm/zsmalloc: use a proper page type
> > config: riscv-randconfig-r033-20230517 (https://download.01.org/0day-ci/archive/20240710/202407100540.VWczFcnh-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/20240710/202407100540.VWczFcnh-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/202407100540.VWczFcnh-lkp@intel.com/
> > 
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> 
> I assume this is completely unrelated to my commit. If not, please someone
> shout :)

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.

> 
> -- 
> Cheers,
> 
> David / dhildenb
> 
> 

      reply	other threads:[~2024-07-11  2:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 21:55 [linux-next:master 9094/10451] WARNING: modpost: vmlinux: section mismatch in reference: remove_device+0x4e (section: .text) -> .L604 (section: .init.text) kernel test robot
2024-07-10  3:03 ` David Hildenbrand
2024-07-11  2:24   ` 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=Zo9CWFsJWComLMjK@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=senozhatsky@chromium.org \
    /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.