rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Cc: rust-for-linux@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
	"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@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Wedson Almeida Filho" <walmeida@microsoft.com>,
	"Nell Shamrell-Harrington" <nells@linux.microsoft.com>,
	"Dirk Behme" <dirk.behme@gmail.com>,
	"Konstantin Andrikopoulos" <kernel@mandragore.io>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Roland Xu" <mu001999@outlook.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: workqueue: define built-in bh queues
Date: Sat, 22 Feb 2025 06:15:47 +0200	[thread overview]
Message-ID: <Z7lPcy6mgOVSFhZr@kernel.org> (raw)
In-Reply-To: <20250221223533.158959-1-hamzamahfooz@linux.microsoft.com>

On Fri, Feb 21, 2025 at 05:35:31PM -0500, Hamza Mahfooz wrote:
> We provide these methods because it lets us access these queues from
> Rust without using unsafe code.
> 
> Signed-off-by: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>

Just getting familiar how code testing and reviews go with Rust code,
as I might put out even a driver at some point of time, so let's give
this a shot :-)

Using 1st person plural is usually almost a cardinal sin almost and is
somewhat exhausting to read. "These methods" refer to nothing and the
commit message does not educate me why the accessors are needed.

It should be IMHO language agnostic that commit message is more
important than the source code. It weights now even more than ever
before because it is also AI acid test. The current commit message
is as good as it did not exist at all.

Based on these conclusions I'd start the commit message by saying
that "Provide safe accessors to the workqueue bottom-halves."

Then add another sentence on why they are required (i.e. who will
be  the caller for these).

BR, Jarkko 

  parent reply	other threads:[~2025-02-22  4:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 22:35 [PATCH] rust: workqueue: define built-in bh queues Hamza Mahfooz
2025-02-21 22:45 ` Miguel Ojeda
2025-02-22  4:17   ` Jarkko Sakkinen
2025-02-22  4:37     ` Jarkko Sakkinen
2025-02-22  4:41       ` Boqun Feng
2025-02-22  6:04         ` Jarkko Sakkinen
2025-02-22 11:57           ` Miguel Ojeda
2025-02-24 17:26             ` Tejun Heo
2025-02-22  4:15 ` Jarkko Sakkinen [this message]
2025-02-22 11:53   ` Miguel Ojeda
2025-02-24 17:19 ` Tejun Heo

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=Z7lPcy6mgOVSFhZr@kernel.org \
    --to=jarkko@kernel.org \
    --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=dirk.behme@gmail.com \
    --cc=gary@garyguo.net \
    --cc=hamzamahfooz@linux.microsoft.com \
    --cc=kernel@mandragore.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mu001999@outlook.com \
    --cc=nells@linux.microsoft.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=walmeida@microsoft.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).