From: Andreas Hindborg <a.hindborg@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Will Deacon" <will@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Gary Guo" <gary@garyguo.net>, "Miguel Ojeda" <ojeda@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2 1/2] rust: atomic: add fetch_sub
Date: Thu, 19 Feb 2026 14:34:21 +0100 [thread overview]
Message-ID: <87qzqgamci.fsf@kernel.org> (raw)
In-Reply-To: <CANiq72=JXKLwSDtS2TPr4zy=nEjKOPTKcG+Yg0U4u+GU07WwdA@mail.gmail.com>
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> writes:
> On Thu, Feb 19, 2026 at 1:20 PM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>>
>> + fn fetch_sub[acquire, release, relaxed](a: &AtomicRepr<Self>, v: Self::Delta) -> Self {
>> + // SAFETY: `a.as_ptr()` is valid and properly aligned.
>> + unsafe { bindings::#call(v, a.as_ptr().cast()) }
>> + }
>
> [ I see `fetch_add` does the same, so it is fine here in this patch
> for consistency, but I thought I would leave a note here anyway... ]
>
> The safety comment, as written, could be read as just saying something
> it is true without justifying it. Something like:
>
> `a.as_ptr()` guarantees the returned pointer is valid and properly aligned.
I'll respin and fix this, for `fetch_add` as well. I can take the
spurious newline you mentioned on same occasion.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-02-19 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 12:20 [PATCH v2 0/2] rust: atomic: add `fetch_sub` and update docs Andreas Hindborg
2026-02-19 12:20 ` [PATCH v2 1/2] rust: atomic: add fetch_sub Andreas Hindborg
2026-02-19 13:20 ` Miguel Ojeda
2026-02-19 13:34 ` Andreas Hindborg [this message]
2026-02-19 12:20 ` [PATCH v2 2/2] rust: atomic: update documentation for `fetch_add` Andreas Hindborg
2026-02-19 12:35 ` Alice Ryhl
2026-02-19 13:10 ` Miguel Ojeda
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=87qzqgamci.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mark.rutland@arm.com \
--cc=miguel.ojeda.sandonis@gmail.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