[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72kf3HY1FUwRVTGGGQVOXxgBkfurHustX6VfM3kYrz-3iA@mail.gmail.com>
Date: Tue, 29 Apr 2025 23:05:55 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Miguel Ojeda <ojeda@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...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 <benno.lossin@...ton.me>, 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, patches@...ts.linux.dev
Subject: Re: [PATCH] rust: device: allow `dead_code` for `Device<>::parent()`
On Tue, Apr 29, 2025 at 10:55 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> Well, that is much better, thanks!
>
> I prefer this then, I really want to catch if some other code starts using this.
You're welcome! I will send v2 then, in case it is not "fixup"ed.
Cheers,
Miguel
Powered by blists - more mailing lists