From: Oliver Sang <oliver.sang@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: Re: error[E0609]: no field `cpu` on type `&bindings::cpufreq_policy`
Date: Thu, 4 Dec 2025 12:50:58 +0800 [thread overview]
Message-ID: <aTETMp6lr75IPXBg@xsang-OptiPlex-9020> (raw)
In-Reply-To: <vacix7xdfokw3m25ekthitv2f2bhiuicqq63ww22qn34mylfof@tddok7combvo>
hi, Viresh,
On Wed, Dec 03, 2025 at 12:56:10PM +0530, Viresh Kumar wrote:
> On 03-12-25, 12:09, kernel test robot wrote:
> > Hi Viresh,
> >
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 3f9f0252130e7dd60d41be0802bf58f6471c691d
> > commit: 6ebdd7c9317737123b260a24e2780018008f1295 rust: cpufreq: Extend abstractions for policy and driver ops
> > date: 7 months ago
> > config: arm-randconfig-r121-20251201 (https://download.01.org/0day-ci/archive/20251203/202512031219.3OgecL5W-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/20251203/202512031219.3OgecL5W-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/202512031219.3OgecL5W-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > >> error[E0609]: no field `cpu` on type `&bindings::cpufreq_policy`
> > --> rust/kernel/cpufreq.rs:462:23
> > |
> > 462 | self.as_ref().cpu
> > | ^^^ unknown field
>
> Is this still the case ? I wasn't able to reproduce the LKP setup, getting some
> failures. Can you provide: rust/bindings/bindings_generated.rs from the build
> folder ?
sorry for false positive. we confirmed this is an issue caused by a bug in
bindgen - https://github.com/rust-lang/rust-bindgen/issues/3264
after we upgrading to bindgen-0.72.1, the issue gone.
>
> --
> viresh
>
next prev parent reply other threads:[~2025-12-04 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 4:09 error[E0609]: no field `cpu` on type `&bindings::cpufreq_policy` kernel test robot
2025-12-03 7:26 ` Viresh Kumar
2025-12-04 4:50 ` Oliver Sang [this message]
2025-12-04 5:14 ` Viresh Kumar
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=aTETMp6lr75IPXBg@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viresh.kumar@linaro.org \
/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