From: David Christensen <drc@linux.ibm.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
David Christensen <drc@linux.ibm.com>
Subject: [PATCH net-next 0/2] net: remove the orphaned IBM eHEA driver
Date: Mon, 29 Jun 2026 16:13:41 -0500 [thread overview]
Message-ID: <20260629211343.3712775-1-drc@linux.ibm.com> (raw)
The IBM eHEA (Ethernet Host Ethernet Adapter) driver has been orphaned
since April 2024 with no active maintainer stepping forward. This series
removes the driver and associated references from the kernel tree.
The driver was marked as an Orphan on April 18, 2024:
commit 97ec32b583bb ("MAINTAINERS: eth: mark IBM eHEA as an Orphan")
In the 13 months since, no maintainer has stepped forward to take
ownership.
The hardware was last supported on IBM POWER7 systems, which reached
end-of-support in December 2020. The driver has received no functional
updates since October 2022:
commit 0e7ce23a917a ("net: ehea: fix possible memory leak in ehea_register_port()")
And has only received mechanical API migrations affecting the entire kernel
tree since that time.
David Christensen (2):
ehea: remove the ehea driver
powerpc: remove ehea driver references
MAINTAINERS | 5 -
arch/powerpc/configs/ppc64_defconfig | 1 -
arch/powerpc/mm/mem.c | 6 -
drivers/net/ethernet/ibm/Kconfig | 9 -
drivers/net/ethernet/ibm/Makefile | 1 -
drivers/net/ethernet/ibm/ehea/Makefile | 7 -
drivers/net/ethernet/ibm/ehea/ehea.h | 477 ---
drivers/net/ethernet/ibm/ehea/ehea_ethtool.c | 277 --
drivers/net/ethernet/ibm/ehea/ehea_hw.h | 253 --
drivers/net/ethernet/ibm/ehea/ehea_main.c | 3581 ------------------
drivers/net/ethernet/ibm/ehea/ehea_phyp.c | 612 ---
drivers/net/ethernet/ibm/ehea/ehea_phyp.h | 433 ---
drivers/net/ethernet/ibm/ehea/ehea_qmr.c | 999 -----
drivers/net/ethernet/ibm/ehea/ehea_qmr.h | 390 --
14 files changed, 7051 deletions(-)
delete mode 100644 drivers/net/ethernet/ibm/ehea/Makefile
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea.h
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_ethtool.c
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_hw.h
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_main.c
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_phyp.c
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_phyp.h
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_qmr.c
delete mode 100644 drivers/net/ethernet/ibm/ehea/ehea_qmr.h
--
2.47.3
next reply other threads:[~2026-06-29 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 21:13 David Christensen [this message]
2026-06-29 21:13 ` [PATCH net-next 1/2] ehea: remove the ehea driver David Christensen
2026-06-30 5:42 ` Christophe Leroy (CS GROUP)
2026-06-29 21:13 ` [PATCH net-next 2/2] powerpc: remove ehea driver references David Christensen
2026-06-30 5:43 ` Christophe Leroy (CS GROUP)
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=20260629211343.3712775-1-drc@linux.ibm.com \
--to=drc@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.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