[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <01000195881dce87-c9f1ac46-3896-47f7-87de-84de94617a54-000000@email.amazonses.com>
Date: Wed, 12 Mar 2025 02:10:09 +0000
From: Antonio Hickey <contact@...oniohickey.com>
To: miguel.ojeda.sandonis@...il.com
Cc: a.hindborg@...nel.org, alex.gaynor@...il.com, aliceryhl@...gle.com,
benno.lossin@...ton.me, bjorn3_gh@...tonmail.com,
boqun.feng@...il.com, contact@...oniohickey.com, dakr@...nel.org,
gary@...yguo.net, justinstitt@...gle.com,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev, morbo@...gle.com,
nathan@...nel.org, nick.desaulniers+lkml@...il.com, ojeda@...nel.org,
rust-for-linux@...r.kernel.org, tmgross@...ch.edu
Subject: Re: [PATCH v2] rust: uaccess: mark UserSliceReader methods inline
On Wed, Mar 12, 2025 at 02:56:26AM +0100, Miguel Ojeda wrote:
> The Suggested-by tag is meant to explain who suggested it, rather than
> duplicate the link -- please see:
>
> https://docs.kernel.org/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
>
> (I typically also put the Link after the tag, if the link is meant to
> show the original suggestion, just like the documentation requests for
> the Reported-by/Closes pair)
>
> In any case, there is no need to re-send a v3 just for this, you can
> wait to see if there is any feedback.
Ahh ok yea the Suggested-by tag makes a lot more sense now haha had a feeling duplicating
the link wasn't right, but was more hesitant to mark someone in specific as suggested by.
Will make note of this for my future patches.
Thanks,
Antonio
Powered by blists - more mailing lists