From: Boqun Feng <boqun.feng@gmail.com>
To: Gary Guo <gary@garyguo.net>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"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>,
"Danilo Krummrich" <dakr@kernel.org>,
"Will Deacon" <will@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Mark Rutland" <mark.rutland@arm.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] MAINTAINERS: update atomic infrastructure entry to include Rust
Date: Wed, 19 Feb 2025 13:13:25 -0800 [thread overview]
Message-ID: <Z7ZJdZpvhMii9y1L@boqun-archlinux> (raw)
In-Reply-To: <20250219201602.1898383-5-gary@garyguo.net>
Hi,
On Wed, Feb 19, 2025 at 08:15:33PM +0000, Gary Guo wrote:
> Suggested-by: Boqun Feng <boqun.feng@gmail.com>
> Signed-off-by: Gary Guo <gary@garyguo.net>
Thanks for doing this!
Acked-by: Boqun Feng <boqun.feng@gmail.com>
Maybe you could add a few things in the commit log, since you're adding
yourself as a reviewer, feel free to add things like:
"I would like to help review atomic related patches, especially Rust
related ones, hence add myself as an reviewer".
I.e. you could mention the areas you will help review ;-)
Regards,
Boqun
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c8d9e8187eb0..55d303633598 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3725,12 +3725,14 @@ M: Will Deacon <will@kernel.org>
> M: Peter Zijlstra <peterz@infradead.org>
> R: Boqun Feng <boqun.feng@gmail.com>
> R: Mark Rutland <mark.rutland@arm.com>
> +R: Gary Guo <gary@garyguo.net>
> L: linux-kernel@vger.kernel.org
> S: Maintained
> F: Documentation/atomic_*.txt
> F: arch/*/include/asm/atomic*.h
> F: include/*/atomic*.h
> F: include/linux/refcount.h
> +F: rust/kernel/sync/refcount.rs
> F: scripts/atomic/
>
> ATTO EXPRESSSAS SAS/SATA RAID SCSI DRIVER
> --
> 2.47.2
>
prev parent reply other threads:[~2025-02-19 21:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 20:15 [PATCH v3 0/4] implement `kernel::sync::Refcount` and convert users Gary Guo
2025-02-19 20:15 ` [PATCH v3 1/4] rust: implement `kernel::sync::Refcount` Gary Guo
2025-02-19 22:12 ` Tamir Duberstein
2025-02-21 16:02 ` Gary Guo
2025-02-21 17:23 ` Tamir Duberstein
2025-02-20 12:46 ` Fiona Behrens
2025-02-19 20:15 ` [PATCH v3 2/4] rust: convert `Arc` to use `Refcount` Gary Guo
2025-02-19 22:12 ` Tamir Duberstein
2025-02-21 16:14 ` Gary Guo
2025-02-21 17:27 ` Tamir Duberstein
2025-02-21 18:28 ` Gary Guo
2025-02-21 18:33 ` Tamir Duberstein
2025-02-21 12:05 ` Alice Ryhl
2025-02-19 20:15 ` [PATCH v3 3/4] rust: block: convert `block::mq` " Gary Guo
2025-02-19 22:26 ` Tamir Duberstein
2025-02-19 22:53 ` Tamir Duberstein
2025-02-20 19:18 ` Andreas Hindborg
2025-02-20 12:27 ` David Gow
2025-02-19 20:15 ` [PATCH v3 4/4] MAINTAINERS: update atomic infrastructure entry to include Rust Gary Guo
2025-02-19 21:13 ` Boqun Feng [this message]
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=Z7ZJdZpvhMii9y1L@boqun-archlinux \
--to=boqun.feng@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=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
/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).