From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Gaynor <alex.gaynor@gmail.com>, Finn Behrens <me@kloenk.de>,
Adam Bratschi-Kaye <ark.email@gmail.com>,
Wedson Almeida Filho <wedsonaf@google.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Sven Van Asbroeck <thesven73@gmail.com>,
Gary Guo <gary@garyguo.net>,
Boris-Chengbiao Zhou <bobo1239@web.de>,
Boqun Feng <boqun.feng@gmail.com>,
Douglas Su <d0u9.su@outlook.com>,
Dariusz Sosnowski <dsosnowski@dsosnowski.pl>,
Antonio Terceiro <antonio.terceiro@linaro.org>,
Daniel Xu <dxu@dxuuu.xyz>, Miguel Cano <macanroj@gmail.com>
Subject: Re: [linux-next:master 12379/15002] include/linux/random.h:29:39: error: use of undeclared identifier 'latent_entropy'
Date: Tue, 5 Apr 2022 20:47:58 +0200 [thread overview]
Message-ID: <CANiq72ni-ePOaDoW8_XmSAoVuX9tv6fbPUoNAq3QOH0KCec13w@mail.gmail.com> (raw)
In-Reply-To: <202204030402.Ps8X1oHd-lkp@intel.com>
Hi LKP,
On Sat, Apr 2, 2022 at 10:47 PM kernel test robot <lkp@intel.com> wrote:
>
> >> include/linux/random.h:29:39: error: use of undeclared identifier 'latent_entropy'
> include/linux/random.h:30:17: error: use of undeclared identifier 'latent_entropy'
> >> include/linux/random.h:29:39: error: use of undeclared identifier 'latent_entropy', err: true
> include/linux/random.h:30:17: error: use of undeclared identifier 'latent_entropy', err: true
> thread 'main' panicked at 'Unable to generate bindings: ()', /opt/cross/rustc-1.59.0-bindgen-0.56.0/cargo/registry/src/github.com-1ecc6299db9ec823/bindgen-0.56.0/src/main.rs:54:36
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Thanks for the report -- fixed.
Cheers,
Miguel
prev parent reply other threads:[~2022-04-05 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 20:46 kernel test robot
2022-04-05 18:47 ` Miguel Ojeda [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=CANiq72ni-ePOaDoW8_XmSAoVuX9tv6fbPUoNAq3QOH0KCec13w@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=antonio.terceiro@linaro.org \
--cc=ark.email@gmail.com \
--cc=bobo1239@web.de \
--cc=boqun.feng@gmail.com \
--cc=d0u9.su@outlook.com \
--cc=dsosnowski@dsosnowski.pl \
--cc=dxu@dxuuu.xyz \
--cc=gary@garyguo.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=macanroj@gmail.com \
--cc=me@kloenk.de \
--cc=mpe@ellerman.id.au \
--cc=ojeda@kernel.org \
--cc=thesven73@gmail.com \
--cc=wedsonaf@google.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