From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/3] net: phy: realtek: rename realtek.c to realtek_main.c
Date: Fri, 10 Jan 2025 12:40:14 +0000 [thread overview]
Message-ID: <Z4EVLteK6aU10PSr@shell.armlinux.org.uk> (raw)
In-Reply-To: <b67681db-76f2-46fa-9e87-48603b7ee081@gmail.com>
On Fri, Jan 10, 2025 at 12:47:39PM +0100, Heiner Kallweit wrote:
> In preparation of adding a source file with hwmon support, rename
> realtek.c to realtek_main.c.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/net/phy/Makefile | 1 +
> drivers/net/phy/{realtek.c => realtek_main.c} | 0
> 2 files changed, 1 insertion(+)
> rename drivers/net/phy/{realtek.c => realtek_main.c} (100%)
Is it worth considering a vendor subdirectory when PHYs end up with
multiple source files?
We already have aquantia, mediatek, mscc, and qcom. Should we be
considering it for this as well?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-01-10 12:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 11:45 [PATCH net-next 0/3] net: phy: realtek: add hwmon support Heiner Kallweit
2025-01-10 11:46 ` [PATCH net-next 1/3] net: phy: realtek: add support for reading MDIO_MMD_VEND2 regs on RTL8125/RTL8126 Heiner Kallweit
2025-01-10 11:47 ` [PATCH net-next 2/3] net: phy: realtek: rename realtek.c to realtek_main.c Heiner Kallweit
2025-01-10 12:40 ` Russell King (Oracle) [this message]
2025-01-10 20:35 ` Heiner Kallweit
2025-01-10 11:48 ` [PATCH net-next 3/3] net: phy: realtek: add hwmon support for temp sensor on RTL822x Heiner Kallweit
2025-01-10 21:10 ` Andrew Lunn
2025-01-10 21:41 ` Heiner Kallweit
2025-01-11 0:20 ` Guenter Roeck
2025-01-11 8:52 ` Heiner Kallweit
2025-01-11 0:08 ` Guenter Roeck
2025-01-11 10:16 ` Heiner Kallweit
2025-01-11 17:00 ` Andrew Lunn
2025-01-11 17:32 ` Heiner Kallweit
2025-01-11 17:44 ` Andrew Lunn
2025-01-11 18:06 ` Heiner Kallweit
2025-01-11 8:52 ` kernel test robot
2025-01-11 9:48 ` kernel test robot
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=Z4EVLteK6aU10PSr@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).