From: kernel test robot <lkp@intel.com>
To: Josef Zoller <josef@walterzollerpiano.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Josef Zoller" <josef@walterzollerpiano.com>
Subject: Re: [PATCH 1/3] rust: char_dev: add character device abstraction
Date: Thu, 17 Oct 2024 19:38:23 +0800 [thread overview]
Message-ID: <202410171902.1Oyg06At-lkp@intel.com> (raw)
In-Reply-To: <20241011-rust-char-dev-v1-1-350225ae228b@walterzollerpiano.com>
Hi Josef,
kernel test robot noticed the following build errors:
[auto build test ERROR on ce1c54fdff7c4556b08f5b875a331d8952e8b6b7]
url: https://github.com/intel-lab-lkp/linux/commits/Josef-Zoller/rust-char_dev-add-character-device-abstraction/20241012-030853
base: ce1c54fdff7c4556b08f5b875a331d8952e8b6b7
patch link: https://lore.kernel.org/r/20241011-rust-char-dev-v1-1-350225ae228b%40walterzollerpiano.com
patch subject: [PATCH 1/3] rust: char_dev: add character device abstraction
config: x86_64-randconfig-016-20241017 (https://download.01.org/0day-ci/archive/20241017/202410171902.1Oyg06At-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241017/202410171902.1Oyg06At-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/202410171902.1Oyg06At-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0658]: associated type bounds are unstable
--> rust/kernel/char_dev.rs:140:42
|
140 | type OpenPtr: for<'a> ForeignOwnable<Borrowed<'a>: Deref<Target: OpenCharDevice>>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #52662 <https://github.com/rust-lang/rust/issues/52662> for more information
= help: add `#![feature(associated_type_bounds)]` to the crate attributes to enable
= note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date
--
>> error[E0658]: associated type bounds are unstable
--> rust/kernel/char_dev.rs:140:62
|
140 | type OpenPtr: for<'a> ForeignOwnable<Borrowed<'a>: Deref<Target: OpenCharDevice>>;
| ^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #52662 <https://github.com/rust-lang/rust/issues/52662> for more information
= help: add `#![feature(associated_type_bounds)]` to the crate attributes to enable
= note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-17 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 18:55 [PATCH 0/3] Character device abstractions for Rust Josef Zoller
2024-10-11 18:55 ` [PATCH 1/3] rust: char_dev: add character device abstraction Josef Zoller
2024-10-12 7:36 ` Greg Kroah-Hartman
2024-10-12 21:48 ` Josef Zoller
2024-10-17 11:38 ` kernel test robot [this message]
2024-10-11 18:55 ` [PATCH 2/3] rust: macros: add IoctlCommand derive macro Josef Zoller
2024-10-11 18:55 ` [PATCH 3/3] samples: rust: add character device sample Josef Zoller
2024-10-12 12:37 ` Greg Kroah-Hartman
2024-10-12 23:38 ` Josef Zoller
2024-10-12 7:29 ` [PATCH 0/3] Character device abstractions for Rust Greg Kroah-Hartman
2024-10-12 21:14 ` Josef Zoller
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=202410171902.1Oyg06At-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=josef@walterzollerpiano.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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;
as well as URLs for NNTP newsgroup(s).