From: Igor Korotin <igor.korotin@yahoo.com>
To: Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Benno Lossin <benno.lossin@proton.me>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org
Subject: [PATCH v3] rust: macros: Fix macro referencing core and kernel crates
Date: Mon, 31 Mar 2025 10:47:09 +0100 [thread overview]
Message-ID: <20250331101325.2357367-2-igor.korotin@yahoo.com> (raw)
In-Reply-To: <D8S8C5W0FCVD.1LH1E86H6PXZD@proton.me>
Took into account all the remarks. Hope this letter with the patch covers
all of them.
Thanks
Igor Korotin
next prev parent reply other threads:[~2025-03-31 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 0:49 [PATCH] rust: macros: Fix macro referencing core and kernel crates Benno Lossin
2025-03-28 18:03 ` [PATCH v2 0/1] rust: macros: Fix macro referencing core and kernel crates v2 Igor Korotin
2025-03-28 18:03 ` [PATCH v2 1/1] " Igor Korotin
2025-03-28 21:50 ` Benno Lossin
2025-03-31 9:47 ` Igor Korotin [this message]
2025-03-31 10:55 ` [PATCH v3] rust: macros: Fix macro referencing core and kernel crates Miguel Ojeda
2025-03-31 10:24 ` [PATCH] " Igor Korotin
2025-03-31 17:01 ` [PATCH] docs: rust: quick-start: update Ubuntu instructions Igor Korotin
2025-03-31 18:30 ` Miguel Ojeda
[not found] ` <44928637.255825.1743501279791@mail.yahoo.com>
2025-04-01 11:26 ` Miguel Ojeda
2025-04-01 13:38 ` Igor Korotin
2025-04-01 14:07 ` Miguel Ojeda
2025-03-31 19:11 ` Benno Lossin
2025-03-29 12:28 ` [PATCH v2 1/1] rust: macros: Fix macro referencing core and kernel crates v2 Miguel Ojeda
2025-03-28 21:48 ` [PATCH v2 0/1] " Benno Lossin
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=20250331101325.2357367-2-igor.korotin@yahoo.com \
--to=igor.korotin@yahoo.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=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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.