From: "Benno Lossin" <lossin@kernel.org>
To: "Boqun Feng" <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
lkmm@lists.linux.dev, linux-arch@vger.kernel.org,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"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>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Lyude Paul" <lyude@redhat.com>, "Ingo Molnar" <mingo@kernel.org>,
"Mitchell Levy" <levymitchell0@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Alan Stern" <stern@rowland.harvard.edu>
Subject: Re: [PATCH v8 6/9] rust: sync: atomic: Add the framework of arithmetic operations
Date: Tue, 19 Aug 2025 00:49:22 +0200 [thread overview]
Message-ID: <DC5X5AJHD5XZ.1QNTV43HZ2F9L@kernel.org> (raw)
In-Reply-To: <aKFGtzQnUdH4zUGD@tardis-2.local>
On Sun Aug 17, 2025 at 5:04 AM CEST, Boqun Feng wrote:
> On Sat, Aug 16, 2025 at 09:35:26PM +0200, Benno Lossin wrote:
>> On Sat Aug 16, 2025 at 6:10 PM CEST, Boqun Feng wrote:
>> > On Tue, Aug 12, 2025 at 10:04:12AM +0200, Benno Lossin wrote:
>> >> On Sat Jul 19, 2025 at 5:08 AM CEST, Boqun Feng wrote:
>> >> > +/// Types that support atomic add operations.
>> >> > +///
>> >> > +/// # Safety
>> >> > +///
>> >> > +/// `wrapping_add` any value of type `Self::Repr::Delta` obtained by [`Self::rhs_into_delta()`] to
>> >>
>> >> Can you add a normal comment TODO here:
>> >>
>> >> // TODO: properly define `wrapping_add` in this context.
>> >
>> > Yeah, this sounds good to me. How do you propose we arrange the normal
>> > comment with the doc comment, somthing like:
>> >
>> > // TODO: properly define `wrapping_add` in this context.
>> >
>> > /// Types that support atomic add operations.
>> > ///
>> > /// # Safety
>> > ///
>> > /// `wrapping_add` any value of type `Self::Repr::Delta` obtained by [`Self::rhs_into_delta()`] to
>> > ...
>> > pub unsafe trait AtomicAdd<...> {
>> > ...
>> > }
>>
>>
>> Inline maybe?
>>
>> /// Types that support atomic add operations.
>> ///
>> /// # Safety
>> ///
>> // TODO: properly define `wrapping_add` in this context:
>
> The colon looks a bit weird to me. I would replace that with a period,
> i.e.
>
> // TODO: properly define `wrapping_add` in the following comment.
> /// `wrapping_add` any value of type `Self::Repr::Delta` obtained by [`Self::rhs_into_delta()`] to
>
> Thoughts?
Also works for me :)
---
Cheers,
Benno
next prev parent reply other threads:[~2025-08-18 22:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 3:08 [PATCH v8 0/9] LKMM atomics in Rust Boqun Feng
2025-07-19 3:08 ` [PATCH v8 1/9] rust: Introduce atomic API helpers Boqun Feng
2025-07-19 3:08 ` [PATCH v8 2/9] rust: sync: Add basic atomic operation mapping framework Boqun Feng
2025-07-19 3:08 ` [PATCH v8 3/9] rust: sync: atomic: Add ordering annotation types Boqun Feng
2025-08-12 7:52 ` Benno Lossin
2025-07-19 3:08 ` [PATCH v8 4/9] rust: sync: atomic: Add generic atomics Boqun Feng
2025-08-12 7:59 ` Benno Lossin
2025-08-16 16:11 ` Boqun Feng
2025-07-19 3:08 ` [PATCH v8 5/9] rust: sync: atomic: Add atomic {cmp,}xchg operations Boqun Feng
2025-07-19 3:08 ` [PATCH v8 6/9] rust: sync: atomic: Add the framework of arithmetic operations Boqun Feng
2025-08-12 8:04 ` Benno Lossin
2025-08-16 16:10 ` Boqun Feng
2025-08-16 19:35 ` Benno Lossin
2025-08-17 3:04 ` Boqun Feng
2025-08-18 22:49 ` Benno Lossin [this message]
2025-07-19 3:08 ` [PATCH v8 7/9] rust: sync: atomic: Add Atomic<u{32,64}> Boqun Feng
2025-07-19 3:08 ` [PATCH v8 8/9] rust: sync: atomic: Add Atomic<{usize,isize}> Boqun Feng
2025-07-19 3:08 ` [PATCH v8 9/9] rust: sync: Add memory barriers Boqun Feng
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=DC5X5AJHD5XZ.1QNTV43HZ2F9L@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=levymitchell0@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=lyude@redhat.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=torvalds@linux-foundation.org \
--cc=viresh.kumar@linaro.org \
--cc=wedsonaf@gmail.com \
--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).