[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1fd41eb-71e9-f8d9-2607-363c88fd9ab3@gmail.com>
Date: Tue, 9 May 2023 21:39:01 +0100
From: Ben Gooding <ben.gooding.dev@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: alice@...l.io, alex.gaynor@...il.com, benno.lossin@...ton.me,
bjorn3_gh@...tonmail.com, boqun.feng@...il.com, gary@...yguo.net,
linux-kernel@...r.kernel.org, ojeda@...nel.org,
rust-for-linux@...r.kernel.org, wedsonaf@...il.com,
yakoyoku@...il.com
Subject: Re: [PATCH] rust: lock: Reflow long documentation line
Hi Miguel,
On 08/05/2023 21:37, Miguel Ojeda wrote:
> Hi Ben,
>
> On Sun, May 7, 2023 at 6:27 PM Ben Gooding <ben.gooding.dev@...il.com> wrote:
>> Suggested-by: Alice Ryhl <alice@...l.io>
>> Signed-off-by: Ben Gooding <ben.gooding.dev@...il.com>
> Thanks for the patch! Several notes:
>
> - Missing commit message -- in general, please check your patches
> with `scripts/checkpatch.pl` and please read
> https://docs.kernel.org/process/submitting-patches.html.
>
> - This patch goes on top of the previous one you sent but, in the
> kernel workflow, what you are expected to do is send a v2 of your
> patch series instead. You can use `-v2` in `git format-patch` for
> that.
>
> - This patch is not just reflowing as the title implies, but it also
> changes the style of the link -- is there a reason for that? If yes,
> this should be explained.
>
> Cheers,
> Miguel
Thank you very much for your feedback, this is really helpful as I'm
learning the process.
I've submitted a proper v2 of my patch based on your feedback which is
hopefully much more like what you would expect - please let me know.
Many thanks,
Ben
Powered by blists - more mailing lists