From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"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@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 6.10
Date: Sat, 22 Jun 2024 23:55:18 +0200 [thread overview]
Message-ID: <20240622215518.198080-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull this fix for Rust.
It has been in linux-next for more than a week.
No conflicts expected. No changes to the C side.
Thanks!
Cheers,
Miguel
The following changes since commit 83a7eefedc9b56fe7bfeff13b6c7356688ffa670:
Linux 6.10-rc3 (2024-06-09 14:19:43 -0700)
are available in the Git repository at:
https://github.com/Rust-for-Linux/linux.git tags/rust-fixes-6.10
for you to fetch changes up to a126eca844353360ebafa9088d22865cb8e022e3:
rust: avoid unused import warning in `rusttest` (2024-06-11 23:33:28 +0200)
----------------------------------------------------------------
Rust fixes for v6.10
- Avoid unused import warning in 'rusttest'.
----------------------------------------------------------------
Miguel Ojeda (1):
rust: avoid unused import warning in `rusttest`
rust/kernel/alloc/vec_ext.rs | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2024-06-22 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 21:55 Miguel Ojeda [this message]
2024-06-22 22:42 ` [GIT PULL] Rust fixes for 6.10 pr-tracker-bot
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=20240622215518.198080-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@samsung.com \
--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=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wedsonaf@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).