From: Heiner Kallweit <hkallweit1@gmail.com>
To: Realtek linux nic maintainers <nic_swsd@realtek.com>,
Andrew Lunn <andrew+netdev@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>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/3] r8169: merge chip versions
Date: Fri, 18 Apr 2025 11:22:54 +0200 [thread overview]
Message-ID: <5e1e14ea-d60f-4608-88eb-3104b6bbace8@gmail.com> (raw)
After 2b065c098c37 ("r8169: refactor chip version detection") we can
merge handling of few chip versions.
Heiner Kallweit (3):
r8169: merge chip versions 70 and 71 (RTL8126A)
r8169: merge chip versions 64 and 65 (RTL8125D)
r8169: merge chip versions 52 and 53 (RTL8117)
drivers/net/ethernet/realtek/r8169.h | 3 --
drivers/net/ethernet/realtek/r8169_main.c | 36 +++++++------------
.../net/ethernet/realtek/r8169_phy_config.c | 3 --
3 files changed, 12 insertions(+), 30 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-18 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 9:22 Heiner Kallweit [this message]
2025-04-18 9:23 ` [PATCH net-next 1/3] r8169: merge chip versions 70 and 71 (RTL8126A) Heiner Kallweit
2025-04-22 18:57 ` Simon Horman
2025-04-18 9:24 ` [PATCH net-next 2/3] r8169: merge chip versions 64 and 65 (RTL8125D) Heiner Kallweit
2025-04-22 18:58 ` Simon Horman
2025-04-18 9:25 ` [PATCH net-next 3/3] r8169: merge chip versions 52 and 53 (RTL8117) Heiner Kallweit
2025-04-22 18:58 ` Simon Horman
2025-04-24 0:10 ` [PATCH net-next 0/3] r8169: merge chip versions patchwork-bot+netdevbpf
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=5e1e14ea-d60f-4608-88eb-3104b6bbace8@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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).