[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nm-tWGPHMaNF11baVRDFpk8ruvTAVDEWKfraEzADWqQQ@mail.gmail.com>
Date: Wed, 26 Apr 2023 19:55:50 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Ariel Miculas <amiculas@...co.com>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
ojeda@...nel.org, alex.gaynor@...il.com, wedsonaf@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me
Subject: Re: [PATCH] rust: Sort rust/helpers.c's #include directives
On Wed, Apr 26, 2023 at 10:18 AM Ariel Miculas <amiculas@...co.com> wrote:
>
> Sort the #include directives of rust/helpers.c alphabetically and add a
> comment specifying this.
>
> Suggested-by: Miguel Ojeda <ojeda@...nel.org>
> Link: https://github.com/Rust-for-Linux/linux/issues/1003
> Signed-off-by: Ariel Miculas <amiculas@...co.com>
Looks better, and the content is fine!
A few minor notes and tips:
- Please annotate the version of the series when you resubmit a
patch series, e.g. v2, v3, etc. `git-format-patch` can do this for you
via e.g. `-v2`.
- Typically the title would be prefixed like "rust: helpers: sort
includes". In general, try to take a look at a subsystem's pattern for
similar commits.
- The description should also give the rationale for the change,
i.e. the "why" and the "what". This one, for instance, could say that
this is done to improve readability and to be consistent with the
other files with a similar approach within `rust/`.
I can fix these on my side if you prefer, but it may be good practice
if you want to send a quick new version.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists