From: "Ethan D. Twardy" <ethan.twardy@gmail.com>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@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@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Ethan D. Twardy" <ethan.twardy@gmail.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Aswin Unnikrishnan" <aswinunni01@gmail.com>,
rust-for-linux@vger.kernel.org (open list:RUST),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v2 0/4] Enable rustdoc tests for the macros crate
Date: Mon, 1 Jul 2024 06:24:22 -0500 [thread overview]
Message-ID: <20240701112448.28638-1-ethan.twardy@gmail.com> (raw)
Changes from v1:
- Resolve a duplicate kbuild rule identified by the test robot
- Fix a number of formatting issues in the tests
Ethan D. Twardy (4):
kbuild: rust: Expand rusttest target for macros
rust: Enable test for macros::module
rust: macros: Enable use from macro_rules!
rust: macros: Enable the rest of the tests
rust/Makefile | 29 ++++++++--
rust/macros/lib.rs | 126 ++++++++++++++++++++++++++++++++-----------
rust/macros/paste.rs | 15 ++++--
3 files changed, 132 insertions(+), 38 deletions(-)
base-commit: a126eca844353360ebafa9088d22865cb8e022e3
--
2.44.2
next reply other threads:[~2024-07-01 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 11:24 Ethan D. Twardy [this message]
2024-07-01 11:24 ` [PATCH v2 1/4] kbuild: rust: Expand rusttest target for macros Ethan D. Twardy
2024-07-01 11:24 ` [PATCH v2 2/4] rust: Enable test for macros::module Ethan D. Twardy
2024-07-01 11:24 ` [PATCH v2 3/4] rust: macros: Enable use from macro_rules! Ethan D. Twardy
2024-07-01 11:24 ` [PATCH v2 4/4] rust: macros: Enable the rest of the tests Ethan D. Twardy
2024-07-04 9:43 ` Alice Ryhl
2024-07-04 14:49 ` Ethan D. Twardy
2024-07-04 14:58 ` 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=20240701112448.28638-1-ethan.twardy@gmail.com \
--to=ethan.twardy@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=aswinunni01@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).