From: kernel test robot <lkp@intel.com>
To: Boqun Feng <boqun@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [boqun:irqflags 19/20] vmlinux.o: warning: objtool: rust_doctest_kernel_sync_lock_spinlock_rs_1+0x209: rust_helper_local_interrupt_enable() missing __noreturn in .c/.h or NORETURN() in noreturns.h
Date: Mon, 31 Aug 2026 09:25:02 +0200 [thread overview]
Message-ID: <202608310937.YzeF5j5i-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git irqflags
head: d5c6783a39c9f3ae4513eb61038d5306e4ba5f5b
commit: b12fc14f713d1916fc91d5c6bf49c98ab27c45cc [19/20] interrupt: Add {raw_}local_irq_resume()
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260831/202608310937.YzeF5j5i-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260831/202608310937.YzeF5j5i-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/202608310937.YzeF5j5i-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: rust_doctest_kernel_sync_lock_spinlock_rs_1+0x209: rust_helper_local_interrupt_enable() missing __noreturn in .c/.h or NORETURN() in noreturns.h
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-31 7:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608310937.YzeF5j5i-lkp@intel.com \
--to=lkp@intel.com \
--cc=boqun@kernel.org \
--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