[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ-ks9m-xkea1AvsPr264rgBvumCDZqr--fYro1e65O-6XOhgw@mail.gmail.com>
Date: Fri, 4 Jul 2025 16:30:35 -0400
From: Tamir Duberstein <tamird@...il.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "Rafael J. Wysocki" <rafael@...nel.org>,
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>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: devres: remove unused import
On Fri, Jul 4, 2025 at 4:23 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> On 7/4/25 10:11 PM, Tamir Duberstein wrote:
> > As far as I can tell, this was never used.
> >
> > Signed-off-by: Tamir Duberstein <tamird@...il.com>
>
> Do you want me to take this and the other include fixups through the driver-core
> tree or do you need them in rust-next as prerequisite for your CStr series?
If you can take them through the driver-core tree, that would be
great. They're needed for the CStr workstream but not for the first
(out of 5) cycle.
Thanks!
Powered by blists - more mailing lists