From: Danilo Krummrich <dakr@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: FUJITA Tomonori <fujita.tomonori@gmail.com>,
alex.gaynor@gmail.com, gregkh@linuxfoundation.org,
ojeda@kernel.org, rafael@kernel.org, robh@kernel.org,
saravanak@google.com, a.hindborg@kernel.org,
aliceryhl@google.com, bhelgaas@google.com,
bjorn3_gh@protonmail.com, boqun.feng@gmail.com,
david.m.ertman@intel.com, devicetree@vger.kernel.org,
gary@garyguo.net, ira.weiny@intel.com, kwilczynski@kernel.org,
leon@kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, lossin@kernel.org,
netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
tmgross@umich.edu
Subject: Re: [PATCH v3 0/3] rust: Build PHY device tables by using module_device_table macro
Date: Tue, 8 Jul 2025 12:49:47 +0200 [thread overview]
Message-ID: <1b9754c7-b9ad-4b01-8476-3d8367a49635@kernel.org> (raw)
In-Reply-To: <20250707175350.1333bd59@kernel.org>
On 7/8/25 2:53 AM, Jakub Kicinski wrote:
> On Fri, 4 Jul 2025 13:10:00 +0900 FUJITA Tomonori wrote:
>> The PHY abstractions have been generating their own device tables
>> manually instead of using the module_device_table macro provided by
>> the device_id crate. However, the format of device tables occasionally
>> changes [1] [2], requiring updates to both the device_id crate and the custom
>> format used by the PHY abstractions, which is cumbersome to maintain.
>
> Does not apply to networking trees so I suspect someone else will take
> these:
>
> Acked-by: Jakub Kicinski <kuba@kernel.org>
I gave an Acked-by: for patch 1, but can also take it through the driver-core
tree.
- Danilo
prev parent reply other threads:[~2025-07-08 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 4:10 [PATCH v3 0/3] rust: Build PHY device tables by using module_device_table macro FUJITA Tomonori
2025-07-04 4:10 ` [PATCH v3 1/3] rust: device_id: split out index support into a separate trait FUJITA Tomonori
2025-07-09 3:10 ` Trevor Gross
2025-07-11 3:17 ` FUJITA Tomonori
2025-07-04 4:10 ` [PATCH v3 2/3] rust: net::phy represent DeviceId as transparent wrapper over mdio_device_id FUJITA Tomonori
2025-07-09 3:23 ` Trevor Gross
2025-07-11 3:38 ` FUJITA Tomonori
2025-07-04 4:10 ` [PATCH v3 3/3] rust: net::phy Change module_phy_driver macro to use module_device_table macro FUJITA Tomonori
2025-07-09 3:39 ` Trevor Gross
2025-07-08 0:53 ` [PATCH v3 0/3] rust: Build PHY device tables by using " Jakub Kicinski
2025-07-08 10:45 ` Miguel Ojeda
2025-07-08 10:59 ` Danilo Krummrich
2025-07-08 10:59 ` FUJITA Tomonori
2025-07-08 12:47 ` Danilo Krummrich
2025-07-08 18:47 ` Miguel Ojeda
2025-07-08 22:51 ` Danilo Krummrich
2025-07-09 2:08 ` FUJITA Tomonori
2025-07-10 20:01 ` Danilo Krummrich
2025-07-10 23:03 ` FUJITA Tomonori
2025-07-08 10:49 ` Danilo Krummrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b9754c7-b9ad-4b01-8476-3d8367a49635@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=david.m.ertman@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=kuba@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@google.com \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).