From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Alice Ryhl <aliceryhl@google.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: Tue, 31 Dec 2024 16:57:36 +0800 [thread overview]
Message-ID: <Z3OyANq7fAkCs+Qi@rli9-mobl> (raw)
In-Reply-To: <202412311507.14xdiaIX-lkp@intel.com>
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/
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: ccb98ccef0e543c2bd4ef1a72270461957f3d8d0
> commit: 91d39024e1b02914cc5e2dbc137908e29b269ce4 rust: samples: add tracepoint to Rust sample
> date: 8 weeks ago
> config: x86_64-buildonly-randconfig-001-20241230 (https://download.01.org/0day-ci/archive/20241231/202412311507.14xdiaIX-lkp@intel.com/config)
> compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241231/202412311507.14xdiaIX-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/202412311507.14xdiaIX-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> error[E0425]: cannot find value `__tracepoint_rust_sample_loaded` in crate `$crate::bindings`
> --> samples/rust/rust_print.rs:87:5
> |
> 87 | / kernel::declare_trace! {
> 88 | | /// # Safety
> 89 | | ///
> 90 | | /// Always safe to call.
> 91 | | unsafe fn rust_sample_loaded(magic: c_int);
> 92 | | }
> | |_____^ not found in `$crate::bindings`
> |
> = note: this error originates in the macro `kernel::declare_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
> --
> >> error[E0425]: cannot find function `rust_do_trace_rust_sample_loaded` in crate `$crate::bindings`
> --> samples/rust/rust_print.rs:87:5
> |
> 87 | / kernel::declare_trace! {
> 88 | | /// # Safety
> 89 | | ///
> 90 | | /// Always safe to call.
> 91 | | unsafe fn rust_sample_loaded(magic: c_int);
> 92 | | }
> | |_____^ not found in `$crate::bindings`
> |
> = note: this error originates in the macro `kernel::declare_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
next prev parent reply other threads:[~2024-12-31 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 7:15 kernel test robot
2024-12-31 8:57 ` Philip Li [this message]
2025-01-06 11:49 ` Alice Ryhl
2025-01-08 0:56 ` Philip Li
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=Z3OyANq7fAkCs+Qi@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
all inboxes | Powered by JetHome®