From: Philip Li <philip.li@intel.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Andreas Hindborg <a.hindborg@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>, Benno Lossin <lossin@kernel.org>
Subject: Re: [linux-next:master 4752/13171] error[E0609]: no field `__bindgen_anon_1` on type `bindings::kernel_param`
Date: Fri, 5 Dec 2025 10:22:02 +0800 [thread overview]
Message-ID: <aTJBys7oughZ1xjg@rli9-mobl> (raw)
In-Reply-To: <aTJBFhiv+4AB/EzA@xsang-OptiPlex-9020>
On Fri, Dec 05, 2025 at 10:19:02AM +0800, Oliver Sang wrote:
> hi, Andreas Hindborg,
>
> On Thu, Dec 04, 2025 at 12:47:05PM +0100, Andreas Hindborg wrote:
> > Hi Oliver,
> >
> > >
> > > we used 0.72.0 when saw the issues. now we upgraded to 0.72.1 as you used, now
> > > issue disappears.
> >
> > Thanks for confirming!
> >
> > While we could see from the config that you were using bindgen 0.72.0,
> > it was not clear to us where you get this bindgen from. Obtaining
> > bindgen does not seem to be part of the reproducer instructions (or
> > maybe I am not looking in the right place?).
>
> right, for rust, we don't supply instructions how to setup rust env for now.
> sorry for inconvenience.
>
> >
> > If I understand correctly, this issue manifested only when building
> > bindgen 0.72.0 with clang-22-git. Building this was next on our list in
> > trying to reproduce, but getting to that conclusion took a while.
> >
> > Anyway, I want to ask if you can include directions for obtaining or
> > building bindgen in your reproducer instructions?
>
> hi, Philip, can we do this?
yes, let me add this earlier next week to provide extra instructions
for rust build.
>
> >
> > Best regards,
> > Andreas Hindborg
> >
prev parent reply other threads:[~2025-12-05 2:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 20:20 [linux-next:master 4752/13171] error[E0609]: no field `__bindgen_anon_1` on type `bindings::kernel_param` kernel test robot
2025-12-02 21:02 ` Daniel Gomez
2025-12-04 5:57 ` Oliver Sang
2025-12-04 11:47 ` Andreas Hindborg
2025-12-04 11:59 ` Daniel Gomez
2025-12-04 12:24 ` Miguel Ojeda
2025-12-05 0:58 ` Philip Li
2025-12-05 10:43 ` Andreas Hindborg
2025-12-05 11:14 ` Philip Li
2025-12-05 0:51 ` Philip Li
2025-12-05 2:19 ` Oliver Sang
2025-12-05 2:22 ` Philip Li [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=aTJBys7oughZ1xjg@rli9-mobl \
--to=philip.li@intel.com \
--cc=a.hindborg@kernel.org \
--cc=da.gomez@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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