From: Tamir Duberstein <tamird@gmail.com>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>, "Kees Cook" <kees@kernel.org>,
"Fiona Behrens" <me@kloenk.dev>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Asahi Lina" <lina@asahilina.net>
Cc: Boris-Chengbiao Zhou <bobo1239@web.de>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
Tamir Duberstein <tamird@gmail.com>
Subject: [PATCH 0/2] rust: fix rust-analyzer configuration for generated files
Date: Mon, 10 Feb 2025 12:55:52 -0500 [thread overview]
Message-ID: <20250210-rust-analyzer-bindings-include-v1-0-6cbf420e95b6@gmail.com> (raw)
The individual patches should be descriptive on their own. They are
included in a single series because the second patch uses a function
introduced in the first.
I've confirmed this allows me to navigate to symbols defined in
generated files as well as to the generated files themselves. I am using
an out-of-source build.
Signed-off-by: Tamir Duberstein <tamird@gmail.com>
---
Tamir Duberstein (2):
scripts: generate_rust_analyzer.py: add missing include_dirs
scripts: generate_rust_analyzer.py: add uapi crate
scripts/generate_rust_analyzer.py | 41 ++++++++++++++++++++-------------------
1 file changed, 21 insertions(+), 20 deletions(-)
---
base-commit: a64dcfb451e254085a7daee5fe51bf22959d52d3
change-id: 20250210-rust-analyzer-bindings-include-531e9dacec8d
Best regards,
--
Tamir Duberstein <tamird@gmail.com>
next reply other threads:[~2025-02-10 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 17:55 Tamir Duberstein [this message]
2025-02-10 17:55 ` [PATCH 1/2] scripts: generate_rust_analyzer.py: add missing include_dirs Tamir Duberstein
2025-02-10 17:55 ` [PATCH 2/2] scripts: generate_rust_analyzer.py: add uapi crate Tamir Duberstein
2025-02-10 18:02 ` Tamir Duberstein
2025-03-11 23:19 ` [PATCH 0/2] rust: fix rust-analyzer configuration for generated files Miguel Ojeda
2025-03-11 23:21 ` Miguel Ojeda
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=20250210-rust-analyzer-bindings-include-v1-0-6cbf420e95b6@gmail.com \
--to=tamird@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=bobo1239@web.de \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=kees@kernel.org \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kloenk.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=yakoyoku@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.