[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DBZS31MID9U3.2K30H3P4E8BUX@kernel.org>
Date: Mon, 11 Aug 2025 19:35:20 +0200
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Boqun Feng" <boqun.feng@...il.com>
Cc: "Daniel Almeida" <daniel.almeida@...labora.com>, "Miguel Ojeda"
<ojeda@...nel.org>, "Alex Gaynor" <alex.gaynor@...il.com>, "Gary Guo"
<gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, "Andreas Hindborg" <a.hindborg@...nel.org>,
"Alice Ryhl" <aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>, "Rafael J. Wysocki"
<rafael@...nel.org>, "Thomas Gleixner" <tglx@...utronix.de>, "Bjorn
Helgaas" <bhelgaas@...gle.com>, Krzysztof Wilczy´nski
<kwilczynski@...nel.org>, "Benno Lossin" <lossin@...nel.org>,
<linux-kernel@...r.kernel.org>, <rust-for-linux@...r.kernel.org>,
<linux-pci@...r.kernel.org>
Subject: Re: [PATCH v9 7/7] rust: irq: add &Device<Bound> argument to irq
callbacks
On Mon Aug 11, 2025 at 7:11 PM CEST, Boqun Feng wrote:
> I think it's fine to submit with only Alice's SoB, my understanding is
> that you won't necessarily need to add your SoB if you are simply
> re-submitting a patch (with minor changes).
I think it is required for everyone who is handling or transporting the patch in
any way, documenting the exact route a patch has taking while conforming with
the developer’s certificate of origin.
Powered by blists - more mailing lists