linux-kernel - Re: [PATCH v3 0/3] rust: Build PHY device tables by using module_device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250709.110837.298179611860747415.fujita.tomonori@gmail.com>
Date: Wed, 09 Jul 2025 11:08:37 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: dakr@...nel.org
Cc: miguel.ojeda.sandonis@...il.com, fujita.tomonori@...il.com,
 kuba@...nel.org, gregkh@...uxfoundation.org, robh@...nel.org,
 saravanak@...gle.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 Wed, 9 Jul 2025 00:51:24 +0200
Danilo Krummrich <dakr@...nel.org> wrote:

>> Since it touched several subsystems and it is based on rust-next, I am
>> happy to do so, but driver-core makes sense given that is the main
>> change after all.
>> 
>> So if I don't see you picking it, I will eventually do it.
> 
> Checked again and the driver-core tree makes most sense, since we also need to
> fix up the ACPI device ID code, which is queued up in driver-core-next.
> 
> I also caught a missing change in rust/kernel/driver.rs, which most likely
> slipped through by not building with CONFIG_OF. :)

Oops, you are right. I mistakenly thought that CONFIG_OF was enabled
because kernel/of.rs was being compiled.


> Here's the diff to fix up both, I already fixed it up on my end -- no need to
> send a new version.

Thanks a lot!