Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
	<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	"Steven Rostedt (Google)" <rostedt@goodmis.org>,
	Boqun Feng <boqun.feng@gmail.com>
Subject: Re: error[E0425]: cannot find value `__tracepoint_rust_sample_loaded` in crate `$crate::bindings`
Date: Wed, 8 Jan 2025 08:56:48 +0800	[thread overview]
Message-ID: <Z33NUGpt7FM6FKuJ@rli9-mobl> (raw)
In-Reply-To: <CAH5fLghNqbu2LO6SMr2Nsciji5k01tagaAEMZQ-WKJ8b9E56hg@mail.gmail.com>

On Mon, Jan 06, 2025 at 12:49:43PM +0100, Alice Ryhl wrote:
> On Tue, Dec 31, 2024 at 9:58 AM Philip Li <philip.li@intel.com> wrote:
> >
> > On Tue, Dec 31, 2024 at 03:15:47PM +0800, kernel test robot wrote:
> > > Hi Alice,
> > >
> > > FYI, the error/warning still remains.
> >
> > Kindly ignore this report, which had already been discussed in [1]
> >
> > [1] https://lore.kernel.org/oe-kbuild-all/CAH5fLggEzmerC6Qg1fjuc_wiy21BJQGGYdZSZA+KV=oP6q9iJg@mail.gmail.com/
> 
> Would it be possible to upgrade bindgen used by this robot? Please see:
> https://lore.kernel.org/all/CAH5fLgjmtuZ7Sxp49GoGC079sXqS4wmsEmZKM-T4Mh9FycDYGQ@mail.gmail.com/

Sorry, i missed this suggestion. Sure, the bot side will follow up to
upgrade bindgen, so far, it follows scripts/min-tool-version.sh to choose
which version to use.

> 
> Alice

  reply	other threads:[~2025-01-08  0:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-31  7:15 error[E0425]: cannot find value `__tracepoint_rust_sample_loaded` in crate `$crate::bindings` kernel test robot
2024-12-31  8:57 ` Philip Li
2025-01-06 11:49   ` Alice Ryhl
2025-01-08  0:56     ` Philip Li [this message]
2025-01-08  8:40       ` Alice Ryhl
  -- strict thread matches above, loose matches on Subject: below --
2024-12-11  8:19 kernel test robot
2024-12-11 11:49 ` Alice Ryhl

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=Z33NUGpt7FM6FKuJ@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=aliceryhl@google.com \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.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