[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mh9a7RpJpRx1toS4z46cHmeXni1oPTpUdi58wQhyN4xA@mail.gmail.com>
Date: Sat, 21 Jun 2025 18:07:02 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Onur Özkan <work@...rozkan.dev>
Cc: linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com,
gary@...yguo.net, lossin@...nel.org, a.hindborg@...nel.org,
aliceryhl@...gle.com, tmgross@...ch.edu, dakr@...nel.org,
peterz@...radead.org, mingo@...hat.com, will@...nel.org, longman@...hat.com,
felipe_life@...e.com, daniel@...lak.dev, bjorn3_gh@...tonmail.com
Subject: Re: [PATCH 1/3 v4] rust: add C wrappers for `ww_mutex` inline functions
On Sat, Jun 21, 2025 at 5:22 PM Onur Özkan <work@...rozkan.dev> wrote:
>
> #include "workqueue.c"
> #include "xarray.c"
> +#include "ww_mutex.c"
Please keep the list sorted.
Also, a couple nits on the series:
- The title would normally be ... vN 1/M ..., rather than the other
way around. You can make Git generate it for you with `git
format-patch -vN`.
- Typically you want to give a changelog, either per-patch (ideal,
especially for non-trivial patches that change a lot) after the first
`---` line, or per-series (in the cover letter, which is also
generally good to have for multi-patch series).
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists