[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z9RoBMXWsrjg6jjg@cassiopeiae>
Date: Fri, 14 Mar 2025 18:31:48 +0100
From: Danilo Krummrich <dakr@...nel.org>
To: Boqun Feng <boqun.feng@...il.com>
Cc: gregkh@...uxfoundation.org, rafael@...nel.org, bhelgaas@...gle.com,
ojeda@...nel.org, alex.gaynor@...il.com, gary@...yguo.net,
bjorn3_gh@...tonmail.com, benno.lossin@...ton.me,
a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v2 2/4] rust: device: implement device context marker
On Fri, Mar 14, 2025 at 10:21:58AM -0700, Boqun Feng wrote:
> On Fri, Mar 14, 2025 at 05:09:05PM +0100, Danilo Krummrich wrote:
> > Some bus device functions should only be called from bus callbacks,
> > such as probe(), remove(), resume(), suspend(), etc.
> >
> > To ensure this add device context marker structs, that can be used as
> > generics for bus device implementations.
> >
> > Reviewed-by: Benno Lossin <benno.lossin@...ton.me>
> > Suggested-by: Benno Lossin <benno.lossin@...ton.me>
>
> Try chronological order for the tags? It was suggested first and then
> reviewed.
Is that a thing? When I apply patches I usully keep ACKs, RBs and SOBs together
at the bottom.
Powered by blists - more mailing lists