From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/3] r8169: disable detection of further chip versions that didn't make it to the mass market
Date: Mon, 15 Nov 2021 21:50:11 +0100 [thread overview]
Message-ID: <7708d13a-4a2b-090d-fadf-ecdd0fff5d2e@gmail.com> (raw)
There's no sign of life from further chip versions. Seems they didn't
make it to the mass market. Let's disable detection and if nobody
complains remove support a few kernel versions later.
Heiner Kallweit (3):
r8169: disable detection of chip versions 49 and 50
r8169: disable detection of chip version 45
r8169: disable detection of chip version 41
drivers/net/ethernet/realtek/r8169_main.c | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
--
2.33.1
next reply other threads:[~2021-11-15 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 20:50 Heiner Kallweit [this message]
2021-11-15 20:51 ` [PATCH net-next 1/3] r8169: disable detection of chip versions 49 and 50 Heiner Kallweit
2021-11-15 20:51 ` [PATCH net-next 2/3] r8169: disable detection of chip version 45 Heiner Kallweit
2021-11-15 20:52 ` [PATCH net-next 3/3] r8169: disable detection of chip version 41 Heiner Kallweit
2021-11-17 3:20 ` [PATCH net-next 0/3] r8169: disable detection of further chip versions that didn't make it to the mass market patchwork-bot+netdevbpf
2021-11-24 20:44 ` [PATCH net-next] r8169: disable detection of chip version 60 Heiner Kallweit
2021-11-26 3:20 ` 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=7708d13a-4a2b-090d-fadf-ecdd0fff5d2e@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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).