llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH v3 1/3] replace `#[allow(...)]` with `#[expect(...)]`
       [not found] <20250628040956.2181-2-work@onurozkan.dev>
@ 2025-06-29  7:43 ` kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2025-06-29  7:43 UTC (permalink / raw)
  To: Onur Özkan, rust-for-linux, linux-kernel, linux-pm,
	linux-kselftest, kunit-dev
  Cc: llvm, oe-kbuild-all, airlied, simona, ojeda, alex.gaynor,
	boqun.feng, gary, bjorn3_gh, lossin, a.hindborg, aliceryhl,
	tmgross, rafael, viresh.kumar, gregkh, maarten.lankhorst, mripard,
	tzimmermann, davidgow, nm, Onur Özkan

Hi Onur,

kernel test robot noticed the following build warnings:

[auto build test WARNING on driver-core/driver-core-next]
[also build test WARNING on driver-core/driver-core-linus rust/alloc-next shuah-kselftest/kunit shuah-kselftest/kunit-fixes rafael-pm/linux-next rafael-pm/bleeding-edge linus/master v6.16-rc3]
[cannot apply to rust/rust-next driver-core/driver-core-testing rust/pin-init-next amd-pstate/linux-next amd-pstate/bleeding-edge next-20250627]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Onur-zkan/replace-allow-with-expect/20250628-121734
base:   driver-core/driver-core-next
patch link:    https://lore.kernel.org/r/20250628040956.2181-2-work%40onurozkan.dev
patch subject: [PATCH v3 1/3] replace `#[allow(...)]` with `#[expect(...)]`
config: x86_64-randconfig-008-20250629 (https://download.01.org/0day-ci/archive/20250629/202506291507.M9eg5kic-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250629/202506291507.M9eg5kic-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/202506291507.M9eg5kic-lkp@intel.com/

All warnings (new ones prefixed by >>):

   ***
   *** Rust bindings generator 'bindgen' < 0.69.5 together with libclang >= 19.1
   *** may not work due to a bug (https://github.com/rust-lang/rust-bindgen/pull/2824),
   *** unless patched (like Debian's).
   ***   Your bindgen version:  0.65.1
   ***   Your libclang version: 20.1.7
   ***
   ***
   *** Please see Documentation/rust/quick-start.rst for details
   *** on how to set up the Rust support.
   ***
>> warning: this lint expectation is unfulfilled
   --> rust/kernel/opp.rs:603:14
   |
   603 |     #[expect(dead_code)]
   |              ^^^^^^^^^
   |
   = note: `#[warn(unfulfilled_lint_expectations)]` on by default
--
>> warning: this lint expectation is unfulfilled
   --> rust/kernel/opp.rs:605:14
   |
   605 |     #[expect(dead_code)]
   |              ^^^^^^^^^

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-06-29  7:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20250628040956.2181-2-work@onurozkan.dev>
2025-06-29  7:43 ` [PATCH v3 1/3] replace `#[allow(...)]` with `#[expect(...)]` kernel test robot

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 NNTP newsgroup(s).