llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 2/2] rust: add firmware abstractions
Date: Wed, 12 Jun 2024 19:32:03 +0800	[thread overview]
Message-ID: <202406121959.hSkfmD0s-lkp@intel.com> (raw)
In-Reply-To: <20240610180318.72152-3-dakr@redhat.com>

Hi Danilo,

kernel test robot noticed the following build errors:

[auto build test ERROR on 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0]

url:    https://github.com/intel-lab-lkp/linux/commits/Danilo-Krummrich/rust-add-abstraction-for-struct-device/20240611-020558
base:   1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
patch link:    https://lore.kernel.org/r/20240610180318.72152-3-dakr%40redhat.com
patch subject: [PATCH v2 2/2] rust: add firmware abstractions
config: x86_64-randconfig-012-20240612 (https://download.01.org/0day-ci/archive/20240612/202406121959.hSkfmD0s-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240612/202406121959.hSkfmD0s-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/202406121959.hSkfmD0s-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `FromResidual`)
   --> rust/doctests_kernel_generated.rs:373:65
   |
   370 | fn main() { #[allow(non_snake_case)] fn _doctest_main__kbuild_src_consumer_rust_kernel_firmware_rs_27_0() {
   |                                      -------------------------------------------------------------------- this function should return `Result` or `Option` to accept `?`
   ...
   373 | let fw = Firmware::request("path/to/firmware.bin", dev.as_ref())?;
   |                                                                 ^ cannot use the `?` operator in a function that returns `()`
   |
>> = help: the trait `FromResidual<core::result::Result<Infallible, rust_doctest_kernel_build_assert_rs_0::kernel::error::Error>>` is not implemented for `()`
--
>> error[E0425]: cannot find function `driver_load_firmware` in this scope
   --> rust/doctests_kernel_generated.rs:374:1
   |
   374 | driver_load_firmware(fw.data());
   | ^^^^^^^^^^^^^^^^^^^^ not found in this scope

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

       reply	other threads:[~2024-06-12 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240610180318.72152-3-dakr@redhat.com>
2024-06-12 11:32 ` kernel test robot [this message]
2024-06-13  3:36 ` [PATCH v2 2/2] rust: add firmware abstractions 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=202406121959.hSkfmD0s-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dakr@redhat.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;
as well as URLs for NNTP newsgroup(s).