From: FUJITA Tomonori <tomo@flapping.org>
To: dakr@kernel.org
Cc: gary@garyguo.net, fujita.tomonori@gmail.com,
gregkh@linuxfoundation.org, rafael@kernel.org, ojeda@kernel.org,
boqun@kernel.org, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
daniel.almeida@collabora.com, tamird@kernel.org,
acourbot@nvidia.com, work@onurozkan.dev, airlied@gmail.com,
simona@ffwll.ch, bhelgaas@google.com, kwilczynski@kernel.org,
abdiel.janulgue@gmail.com, robin.murphy@arm.com,
david.m.ertman@intel.com, iweiny@kernel.org, leon@kernel.org,
lenb@kernel.org, igor.korotin@linux.dev, robh@kernel.org,
saravanak@kernel.org, viresh.kumar@linaro.org,
m.wilczynski@samsung.com, fustini@kernel.org, guoren@kernel.org,
wefu@redhat.com, ukleinek@kernel.org,
driver-core@lists.linux.dev, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 05/11] rust: net/phy: remove expansion from doc
Date: Fri, 31 Jul 2026 19:45:09 +0900 (JST) [thread overview]
Message-ID: <20260731.194509.1672759045396477102.tomo@flapping.org> (raw)
In-Reply-To: <DKC7J1TB8TZN.1LT1GJ0WP9LR0@kernel.org>
On Thu, 30 Jul 2026 23:01:18 +0200
"Danilo Krummrich" <dakr@kernel.org> wrote:
> On Mon Jun 29, 2026 at 2:39 PM CEST, Gary Guo wrote:
>> The expansion serves little purpose and it can easily diverge.
>>
>> Signed-off-by: Gary Guo <gary@garyguo.net>
>
> I did not pick this one up, as it is not necessarily needed by this series.
>
> However, I agree with the intend and I think it did diverge already before this
> series.
>
> FUJITA, please consider to pick this one up, or let me know if you want me to
> take it.
net/phy changes normally go through netdev, but this one just removes
documentation that is already obsolete, so I think taking it via
driver-core as part of this series is the least work for everyone.
So please take it with the series, unless the netdev folks object.
Thanks,
next prev parent reply other threads:[~2026-07-31 10:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:39 [PATCH v2 00/11] rust: driver: use pointers instead of indices for ID info Gary Guo
2026-06-29 12:39 ` [PATCH v2 01/11] rust: driver: remove `IdTable::id` Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 02/11] rust: driver: simplify `IdArray::new_without_index` Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 03/11] rust: pci: use `Option<&IdInfo>` for device ID info Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 04/11] rust: usb: " Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 05/11] rust: net/phy: remove expansion from doc Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-07-30 21:01 ` Danilo Krummrich
2026-07-31 10:45 ` FUJITA Tomonori [this message]
2026-07-31 10:17 ` FUJITA Tomonori
2026-06-29 12:39 ` [PATCH v2 06/11] rust: driver: centralize device ID handling Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 07/11] rust: driver: remove `$module_table_name` from `module_device_table` Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 08/11] rust: driver: store pointers in `DeviceId` Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 09/11] rust: driver: remove open-coded matching logic Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 10/11] rust: driver: remove duplicate ID table Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-06-29 12:39 ` [PATCH v2 11/11] RFC: rust: driver: support map-like syntax for " Gary Guo
2026-06-30 12:40 ` sashiko-bot
2026-07-30 21:00 ` Danilo Krummrich
2026-07-16 19:18 ` [PATCH v2 00/11] rust: driver: use pointers instead of indices for ID info Danilo Krummrich
2026-07-17 9:40 ` Greg Kroah-Hartman
2026-07-30 21:01 ` (subset) " Danilo Krummrich
2026-08-02 19:27 ` Igor Korotin
2026-08-03 20:55 ` Danilo Krummrich
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=20260731.194509.1672759045396477102.tomo@flapping.org \
--to=tomo@flapping.org \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=david.m.ertman@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=driver-core@lists.linux.dev \
--cc=fujita.tomonori@gmail.com \
--cc=fustini@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@kernel.org \
--cc=igor.korotin@linux.dev \
--cc=iweiny@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=lenb@kernel.org \
--cc=leon@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=m.wilczynski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@kernel.org \
--cc=simona@ffwll.ch \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=ukleinek@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wefu@redhat.com \
--cc=work@onurozkan.dev \
/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