mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, Danilo Krummrich <dakr@kernel.org>,
	Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: error[E0609]: no field `class` on type `bindings::pci_dev`
Date: Mon, 1 Dec 2025 17:33:00 -0800	[thread overview]
Message-ID: <594de273-6e64-4928-8407-1afcccf42479@nvidia.com> (raw)
In-Reply-To: <202512020539.vRk7h3HD-lkp@intel.com>

On 12/1/25 1:24 PM, kernel test robot wrote:
> Hi John,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   7d0a66e4bb9081d75c82ec4957c50034cb0ea449
> commit: ed78a01887e2257cff0412b640db68b70a2654dc rust: pci: provide access to PCI Class and Class-related items
> date:   3 months ago
> config: arm64-randconfig-001-20251202 (https://download.01.org/0day-ci/archive/20251202/202512020539.vRk7h3HD-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project b3428bb966f1de8aa48375ffee0eba04ede133b7)
> rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251202/202512020539.vRk7h3HD-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/202512020539.vRk7h3HD-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>>> error[E0609]: no field `class` on type `bindings::pci_dev`
>    --> rust/kernel/pci.rs:471:51
>    |
>    471 |         Class::from_raw(unsafe { (*self.as_raw()).class })
>    |                                                   ^^^^^ unknown field
>    |
>    = note: available field is: `_address`
> 

I vaguely recall that this is due to an infrastructure shortcoming, which
is being worked on. So I'm mostly ignoring this for now.


thanks,
-- 
John Hubbard


  reply	other threads:[~2025-12-02  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 21:24 kernel test robot
2025-12-02  1:33 ` John Hubbard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-21  7:57 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=594de273-6e64-4928-8407-1afcccf42479@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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

all inboxes | Powered by JetHome®