[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fcfdf9c1-288c-40ce-a8cc-77f540b981b0@kernel.org>
Date: Tue, 8 Jul 2025 12:59:02 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Jakub Kicinski <kuba@...nel.org>, gregkh@...uxfoundation.org,
robh@...nel.org, saravanak@...gle.com,
FUJITA Tomonori <fujita.tomonori@...il.com>, alex.gaynor@...il.com,
ojeda@...nel.org, rafael@...nel.org, a.hindborg@...nel.org,
aliceryhl@...gle.com, bhelgaas@...gle.com, bjorn3_gh@...tonmail.com,
boqun.feng@...il.com, david.m.ertman@...el.com, devicetree@...r.kernel.org,
gary@...yguo.net, ira.weiny@...el.com, kwilczynski@...nel.org,
leon@...nel.org, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
lossin@...nel.org, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org,
tmgross@...ch.edu
Subject: Re: [PATCH v3 0/3] rust: Build PHY device tables by using
module_device_table macro
On 7/8/25 12:45 PM, Miguel Ojeda wrote:
> On Tue, Jul 8, 2025 at 2:53 AM Jakub Kicinski <kuba@...nel.org> wrote:
>>
>> Does not apply to networking trees so I suspect someone else will take
>> these:
>>
>> Acked-by: Jakub Kicinski <kuba@...nel.org>
>
> Thanks! Happy to take it through Rust tree if that is best.
Ah, didn't get this one before I replied in [1]. I gave an ACK because I thought
it's going through the networking tree, but I can also take it through driver-core.
Taking it through the rust tree is fine for me too; just let me know. :)
[1] https://lore.kernel.org/lkml/1b9754c7-b9ad-4b01-8476-3d8367a49635@kernel.org/
Powered by blists - more mailing lists