From: Ingo Molnar <mingo@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [tip:timers/urgent 3/3] llvm-readelf: warning: 'arch/riscv/kernel/vdso/hwprobe.o': bitcode files are not supported
Date: Sun, 4 May 2025 11:51:04 +0200 [thread overview]
Message-ID: <aBc4iLZoH1cFzM96@gmail.com> (raw)
In-Reply-To: <20250504113922-5cc48741-0c27-4384-a77f-c088050bc747@linutronix.de>
* Thomas Weißschuh <thomas.weissschuh@linutronix.de> wrote:
> Hi Ingo,
>
> On Sun, May 04, 2025 at 01:26:54PM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/urgent
> > head: 7aeb1538be5df3efa1d799e5428ac3a0ae802293
> > commit: 7aeb1538be5df3efa1d799e5428ac3a0ae802293 [3/3] vdso: Reject absolute relocations during build
> > :::::: branch date: 4 hours ago
> > :::::: commit date: 4 hours ago
> > config: riscv-randconfig-001-20250503 (https://download.01.org/0day-ci/archive/20250503/202505030636.3ExDB8O2-lkp@intel.com/config)
> > compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250503/202505030636.3ExDB8O2-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/r/202505030636.3ExDB8O2-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> llvm-readelf: warning: 'arch/riscv/kernel/vdso/hwprobe.o': bitcode files are not supported
> > --
> > >> llvm-readelf: warning: 'arch/riscv/kernel/vdso/hwprobe.o': bitcode files are not supported
>
> Could you drop "vdso: Reject absolute relocations during build" from the "urgent"
> branch for now? It is not necessary for the actual bugfix.
Done.
> I have an idea on how to fix the issue found by 0day but those
> patches can then go through the normal process.
Thanks!
I'd still prefer to delay the other timers/urgent fixes to be on the
safe side and send them in a day or two, but it's up to Thomas.
Ingo
next prev parent reply other threads:[~2025-05-04 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 5:26 [tip:timers/urgent 3/3] llvm-readelf: warning: 'arch/riscv/kernel/vdso/hwprobe.o': bitcode files are not supported kernel test robot
2025-05-04 9:42 ` Thomas Weißschuh
2025-05-04 9:51 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-02 22:38 kernel test robot
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=aBc4iLZoH1cFzM96@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=x86@kernel.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.