From: Boqun Feng <boqun@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Ingo Molnar" <mingo@kernel.org>, "Will Deacon" <will@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"Waiman Long" <longman@redhat.com>, "Gary Guo" <gary@garyguo.net>,
"Alice Ryhl" <aliceryhl@google.com>,
"Lyude Paul" <lyude@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: [GIT PULL] [PATCH 0/3] Rust synchronization changes for v7.2
Date: Thu, 4 Jun 2026 22:23:28 -0700 [thread overview]
Message-ID: <20260605052331.1628-1-boqun@kernel.org> (raw)
Hi Peter,
Please pull this small set of changes into tip.
Sorry for being a bit late on this cycle. I was trying to get the
refcounted interrupt change [1] in this PR, but I feel maybe I should
make that a separate patch series for more reviews, which I will send
out shortly.
The following changes since commit 608323bf7bb85bbb647eca4373acef247f105e67:
selftests: futex: Add tests for robust release operations (2026-06-03 11:38:53 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git/ tags/rust-sync-7.2
for you to fetch changes up to 33d221f06eb7e068fd6c3c78d432322f807a3f0f:
rust: sync: completion: Mark inline complete_all and wait_for_completion (2026-06-03 11:52:08 -0700)
----------------------------------------------------------------
Rust synchronization changes for 7.2:
- Add "RUST [SYNC]" maintainer entry.
- locking/lockdep: Replace snprintf with strscpy in seq_stats.
- Mark a few completion related Rust function as inline.
[1]: https://lore.kernel.org/rust-for-linux/20260526152148.30514-1-boqun@kernel.org/
Regards,
Boqun
----------------------------------------------------------------
Boqun Feng (1):
MAINTAINERS: Add RUST [SYNC] entry
Fabricio Parra (1):
rust: sync: completion: Mark inline complete_all and wait_for_completion
Thorsten Blum (1):
locking/lockdep: Replace snprintf with strscpy in seq_stats
MAINTAINERS | 14 ++++++++++++++
kernel/locking/lockdep_proc.c | 5 +++--
rust/kernel/sync/completion.rs | 2 ++
3 files changed, 19 insertions(+), 2 deletions(-)
next reply other threads:[~2026-06-05 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 5:23 Boqun Feng [this message]
2026-06-05 5:23 ` [PATCH 1/3] MAINTAINERS: Add RUST [SYNC] entry Boqun Feng
2026-06-05 5:23 ` [PATCH 2/3] locking/lockdep: Replace snprintf with strscpy in seq_stats Boqun Feng
2026-06-05 5:23 ` [PATCH 3/3] rust: sync: completion: Mark inline complete_all and wait_for_completion Boqun Feng
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=20260605052331.1628-1-boqun@kernel.org \
--to=boqun@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
--cc=work@onurozkan.dev \
/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