[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DBCQKJIBVGGM.1R0QNKO3TE4N0@kernel.org>
Date: Tue, 15 Jul 2025 17:32:50 +0200
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Thomas Gleixner" <tglx@...utronix.de>
Cc: "Miguel Ojeda" <ojeda@...nel.org>, "Daniel Almeida"
<daniel.almeida@...labora.com>, "Alex Gaynor" <alex.gaynor@...il.com>,
"Boqun Feng" <boqun.feng@...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>,
"Bjorn Helgaas" <bhelgaas@...gle.com>,
Krzysztof Wilczyński <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 v7 0/6] rust: add support for request_irq
On Tue Jul 15, 2025 at 5:16 PM CEST, Daniel Almeida wrote:
> Daniel Almeida (6):
> rust: irq: add irq module
> rust: irq: add flags module
> rust: irq: add support for non-threaded IRQs and handlers
> rust: irq: add support for threaded IRQs and handlers
> rust: platform: add irq accessors
> rust: pci: add irq accessors
(Mostly copy-paste from v6 [1].)
What's the intended merge path for this series? Should I take it through
driver-core, in case we make it for the upcoming merge window? I'd assume so,
given that, besides the series also containing platform and PCI patches, it
depends on patches that are in driver-core-next.
@Thomas: Is there any agreement on how the IRQ Rust code should be maintained?
What's your preference?
- Danilo
[1] https://lore.kernel.org/lkml/aGbkfa57bDa1mzI7@pollux/
Powered by blists - more mailing lists