[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <32B71539-BF90-4815-9085-2963F5DD69B5@collabora.com>
Date: Mon, 11 Aug 2025 14:00:47 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Miguel Ojeda <ojeda@...nel.org>,
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>,
Danilo Krummrich <dakr@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Krzysztof Wilczyński <kwilczynski@...nel.org>,
Benno Lossin <lossin@...nel.org>
Cc: 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 11 Aug 2025, at 13:03, Daniel Almeida <daniel.almeida@...labora.com> wrote:
>
> From: Alice Ryhl <aliceryhl@...gle.com>
>
> When working with a bus device, many operations are only possible while
> the device is still bound. The &Device<Bound> type represents a proof in
> the type system that you are in a scope where the device is guaranteed
> to still be bound. Since we deregister irq callbacks when unbinding a
> device, if an irq callback is running, that implies that the device has
> not yet been unbound.
>
> To allow drivers to take advantage of that, add an additional argument
> to irq callbacks.
>
> Signed-off-by: Alice Ryhl <aliceryhl@...gle.com>
Sorry. I forgot to add my SOB here.
Perhaps this can be added when the patch is being applied in order to cut down on the
number of versions, and therefore avoid the extra noise? Otherwise let me know.
Signed-off-by: Daniel Almeida <daniel.almeida@...labora.com>
Powered by blists - more mailing lists