Rust for Linux List
 help / color / mirror / Atom feed
From: Andreas Hindborg <a.hindborg@kernel.org>
To: Mohamed Osama <mohamed.osama189110@gmail.com>, ojeda@kernel.org
Cc: boqun@kernel.org, gary@garyguo.net, bjorn3_gh@protonmail.com,
	lossin@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
	dakr@kernel.org, daniel.almeida@collabora.com, tamird@kernel.org,
	acourbot@nvidia.com, work@onurozkan.dev, longman@redhat.com,
	lyude@redhat.com, linux-block@vger.kernel.org,
	linux-serial@vger.kernel.org, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] rust: introduce DropGuard
Date: Mon, 28 Sep 2026 11:50:53 +0200	[thread overview]
Message-ID: <87h5j9u2ki.fsf@t14s.mail-host-address-is-not-set> (raw)
In-Reply-To: <87jyo5u2nu.fsf@t14s.mail-host-address-is-not-set>

Andreas Hindborg <a.hindborg@kernel.org> writes:

> "Mohamed Osama" <mohamed.osama189110@gmail.com> writes:
>
>> This series adds the Rust kernel DropGuard API and migrates existing
>> cleanup guards in the block, serdev, and locking code to use it.
>>
>> DropGuard is vendored from the Rust standard library and re-exported
>> through kernel::mem.
>>
>> Changes since v3:
>> - Vendor DropGuard in rust/kernel/std_vendor.rs and re-export it from
>>   kernel::mem, following Gary Guo's review.
>> - Remove the DropGuard KUnit tests and Kconfig option since the
>>   implementation is vendored from the standard library.
>> - Keep the existing ScopeGuard API unchanged.
>
>
> Could you allow for at least 24 hours to pass between new versions of
> your patches?
>
>   40 mins. ago [10/10] Mohamed Osama, sashiko-bot@kernel.org, Boqun Feng    [PATCH 4/4] rust: sync: lock: use DropGuard (in 🛠️ ur)
>   Yest. 01:53 [12/12] Mohamed Osama, sashiko-bot@kernel.org, Gary Guo    [PATCH v3 2/5] rust: mem: add DropGuard (in 🛠️ ur)
>     Sat. 18:46 [11/11] Mohamed Osama, sashiko-bot@kernel.org    [PATCH v2 2/5] rust: mem: add DropGuard (in 🛠️ ur)
>   September 16 [2/2]   Mohamed Osama, sashiko-bot@kernel.org    [PATCH v3] rust: mem: add DropGuard (in 🛠️ ur)
>   September 16 [2/2]   Mohamed Osama, sashiko-bot@kernel.org    [PATCH v2] rust: mem: add DropGuard (in 🛠️ ur)
>   September 16 [2/2]   Mohamed Osama, sashiko-bot@kernel.org    [PATCH v1] rust: mem: add DropGuard (in 🛠️ ur)
>   September 16 [2/2]   Mohamed Osama, sashiko-bot@kernel.org    [PATCH] rust: mem: add DropGuard (in 🛠️ ur)
>
> I'm confused about your versioning scheme.
>
> Could you include links to earlier version of the series when you send a
> new version?
>
> The b4 tool handles most of this for you. I would recommend checking it
> out [1].
>
> The first v1 has a link to a github issue. Could you please keep
> including this link? It is helpful for context.
>
> Best regards,
> Andreas Hindborg
>
> [1] https://b4.docs.kernel.org/en/latest/contributor/prep.html

Also please include the rationale for the change in the cover letter and
commit message. Something along the lines of what is in the github issue
would be fine.


Best regards,
Andreas Hindborg



      reply	other threads:[~2026-09-28  9:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Dch07wH15t-1WtaVQW4vdfmtJuwC_4-JLvrWSB8Pk4vfEHO6mQk1FpYG-tCYBllTB3RbpOXpdyNZp84w4PFl1A==@protonmail.internalid>
2026-09-27 10:45 ` [PATCH v4 0/4] rust: introduce DropGuard Mohamed Osama
2026-09-27 10:45   ` [PATCH 1/4] rust: mem: add DropGuard Mohamed Osama
2026-09-27 10:45   ` [PATCH 2/4] rust: block: gen_disk: use DropGuard Mohamed Osama
2026-09-27 10:45   ` [PATCH 3/4] rust: serdev: " Mohamed Osama
2026-09-27 10:45   ` [PATCH 4/4] rust: sync: lock: " Mohamed Osama
2026-09-28  9:03     ` Boqun Feng
2026-09-28  9:48   ` [PATCH v4 0/4] rust: introduce DropGuard Andreas Hindborg
2026-09-28  9:50     ` Andreas Hindborg [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=87h5j9u2ki.fsf@t14s.mail-host-address-is-not-set \
    --to=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=mohamed.osama189110@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --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