From: "Gary Guo" <gary@garyguo.net>
To: "Alice Ryhl" <aliceryhl@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Carlos Llamas" <cmllamas@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"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>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] rust: task: implement == operator for Task
Date: Fri, 27 Feb 2026 12:24:07 +0000 [thread overview]
Message-ID: <DGPQPPOEVDZN.21JXCJC96SVJM@garyguo.net> (raw)
In-Reply-To: <20260227-close-fd-check-current-v2-2-b3347edbb310@google.com>
On Fri Feb 27, 2026 at 9:34 AM GMT, Alice Ryhl wrote:
> It's useful to compare if two tasks are the same task or not. Rust
> Binder wants this to check if a certain task is equal to the group
> leader of current.
>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Gary Guo <gary@garyguo.net>
> ---
> rust/kernel/task.rs | 9 +++++++++
> 1 file changed, 9 insertions(+)
next prev parent reply other threads:[~2026-02-27 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 9:34 [PATCH v2 0/4] rust_binder: check current before closing fds Alice Ryhl
2026-02-27 9:34 ` [PATCH v2 1/4] rust: sync: implement == operator for ARef Alice Ryhl
2026-02-27 12:23 ` Gary Guo
2026-02-27 9:34 ` [PATCH v2 2/4] rust: task: implement == operator for Task Alice Ryhl
2026-02-27 12:24 ` Gary Guo [this message]
2026-02-27 9:34 ` [PATCH v2 3/4] rust_binder: make use of == " Alice Ryhl
2026-02-27 12:24 ` Gary Guo
2026-02-27 9:34 ` [PATCH v2 4/4] rust_binder: check current before closing fds Alice Ryhl
2026-02-27 12:28 ` Gary Guo
2026-02-27 13:02 ` 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=DGPQPPOEVDZN.21JXCJC96SVJM@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®