[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mzbZidoRZALCmO68efnigyxLf0Vv0pLYWVxD0PJPj1Vg@mail.gmail.com>
Date: Fri, 15 Nov 2024 19:00:23 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Alistair Francis <alistair@...stair23.me>, lukas@...ner.de, Jonathan.Cameron@...wei.com,
linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
akpm@...ux-foundation.org, bhelgaas@...gle.com, linux-pci@...r.kernel.org,
linux-cxl@...r.kernel.org, bjorn3_gh@...tonmail.com, ojeda@...nel.org,
tmgross@...ch.edu, boqun.feng@...il.com, benno.lossin@...ton.me,
a.hindborg@...nel.org, wilfred.mallawa@....com, alistair23@...il.com,
alex.gaynor@...il.com, gary@...yguo.net, aliceryhl@...gle.com
Subject: Re: [RFC 1/6] rust: bindings: Support SPDM bindings
On Fri, Nov 15, 2024 at 6:53 PM Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> Usually an additional #include goes in the same patch that makes use
> of the new .h file. Maybe there's a different convention in rust/?
I think doing it in the same patch makes more sense, i.e. please feel
free to avoid a "rust: bindings: ..."-titled patch.
It is also how it has been done in the past, e.g. see commit
de6582833db0 ("rust: add firmware abstractions").
Cheers,
Miguel
Powered by blists - more mailing lists