All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexandru Radovici <alexandru.radovici@wyliodrin.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC 2/2] rust: usb: add control message send and receive
Date: Mon, 10 Aug 2026 14:04:28 +0200	[thread overview]
Message-ID: <202608101304.PBIoqR9D-lkp@intel.com> (raw)
In-Reply-To: <20260801-rust-usb_control_msg-v1-2-655bb444b52c@wyliodrin.com>

Hi Alexandru,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on 8ba098e6b6ff0db8edf28528d1552be261af30d4]

url:    https://github.com/intel-lab-lkp/linux/commits/Alexandru-Radovici/rust-usb-add-endpoint-abstraction/20260804-141353
base:   8ba098e6b6ff0db8edf28528d1552be261af30d4
patch link:    https://lore.kernel.org/r/20260801-rust-usb_control_msg-v1-2-655bb444b52c%40wyliodrin.com
patch subject: [PATCH RFC 2/2] rust: usb: add control message send and receive
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260810/202608101304.PBIoqR9D-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/20260810/202608101304.PBIoqR9D-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/202608101304.PBIoqR9D-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> warning: unresolved link to `Self::max_packet_mult`
   --> rust/kernel/usb/endpoint.rs:321:66
   |
   321 |     /// transactions per microframe, which [`max_packet_mult()`](Self::max_packet_mult)
   |                                                                  ^^^^^^^^^^^^^^^^^^^^^ the struct `HostEndpoint` has no field or associated item named `max_packet_mult`
--
>> warning: unresolved link to `Interface::current_alt_setting`
   --> rust/kernel/usb.rs:346:29
   |
   346 | /// active at a time; see [`Interface::current_alt_setting()`].
   |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the struct `Interface` has no function named `current_alt_setting`
--
>> warning: unresolved link to `Endpoint::as_in`
   --> rust/kernel/usb.rs:391:11
   |
   391 |     /// [`Endpoint::as_in()`], [`Endpoint::as_out()`] and [`Endpoint::as_control()`].
   |           ^^^^^^^^^^^^^^^^^ no item named `Endpoint` in scope
--
>> warning: unresolved link to `Endpoint::as_out`
   --> rust/kernel/usb.rs:391:34
   |
   391 |     /// [`Endpoint::as_in()`], [`Endpoint::as_out()`] and [`Endpoint::as_control()`].
   |                                  ^^^^^^^^^^^^^^^^^^ no item named `Endpoint` in scope
--
>> warning: unresolved link to `Endpoint::as_control`
   --> rust/kernel/usb.rs:391:61
   |
   391 |     /// [`Endpoint::as_in()`], [`Endpoint::as_out()`] and [`Endpoint::as_control()`].
   |                                                             ^^^^^^^^^^^^^^^^^^^^^^ no item named `Endpoint` in scope

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

      parent reply	other threads:[~2026-08-10 12:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  0:01 [PATCH RFC 0/2] rust: usb: abstractions towards the port of usbsevseg.c to Rust Alexandru Radovici
2026-08-01  0:01 ` [PATCH RFC 1/2] rust: usb: add endpoint abstraction Alexandru Radovici
2026-08-02  8:39   ` Greg Kroah-Hartman
2026-08-03 12:46     ` Alrexandru Radovici
2026-08-03 13:23       ` Greg Kroah-Hartman
2026-08-11  9:39         ` Alrexandru Radovici
2026-08-01  0:01 ` [PATCH RFC 2/2] rust: usb: add control message send and receive Alexandru Radovici
2026-08-02  8:32   ` Greg Kroah-Hartman
2026-08-03 11:39     ` Alrexandru Radovici
2026-08-10 12:04   ` kernel test robot [this message]

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=202608101304.PBIoqR9D-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandru.radovici@wyliodrin.com \
    --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 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.