From: Geert Uytterhoeven <geert@linux-m68k.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Jocelyn Falempe <jfalempe@redhat.com>
Subject: Re: [linux-next:master 6880/10451] ld.lld: error: duplicate symbol: init_module
Date: Thu, 4 Jul 2024 10:57:43 +0200 [thread overview]
Message-ID: <CAMuHMdU6Lzpmdo10jUbVJPnq0Q6dpF60L0icjJug_=WiUeY2QQ@mail.gmail.com> (raw)
In-Reply-To: <202407041634.GgIQlOpZ-lkp@intel.com>
On Thu, Jul 4, 2024 at 10:54 AM kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 0b58e108042b0ed28a71cd7edf5175999955b233
Aka next-20240703.
> commit: 294bbd1f2697ff28af7f036b2cb19fee78eb100b [6880/10451] drm/panic: Add support for drawing a monochrome graphical logo
> config: um-allmodconfig (https://download.01.org/0day-ci/archive/20240704/202407041634.GgIQlOpZ-lkp@intel.com/config)
> compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 326ba38a991250a8587a399a260b0f7af2c9166a)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240704/202407041634.GgIQlOpZ-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/202407041634.GgIQlOpZ-lkp@intel.com/
>
> Note: the linux-next/master HEAD 0b58e108042b0ed28a71cd7edf5175999955b233 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> >> ld.lld: error: duplicate symbol: init_module
> >>> defined at drm_drv.c
> >>> drivers/gpu/drm/drm_drv.o:(init_module)
> >>> defined at drm_panic.c
> >>> drivers/gpu/drm/drm_panic.o:(.ltext+0x0)
Should be fixed by commit 54be78446d0ac117 ("drm/panic: Restrict
graphical logo handling to built-in") in next-20240627 and later?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2024-07-04 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 8:53 kernel test robot
2024-07-04 8:57 ` Geert Uytterhoeven [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='CAMuHMdU6Lzpmdo10jUbVJPnq0Q6dpF60L0icjJug_=WiUeY2QQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=jfalempe@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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