From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, arnd@arndb.de,
tsbogend@alpha.franken.de, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, lukas.bulwahn@gmail.com,
stephen@networkplumber.org, shayagr@amazon.com, mw@semihalf.com,
petrm@nvidia.com, wsa+renesas@sang-engineering.com,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next] eth: fealnx: delete the driver for Myson MTD-800
Date: Wed, 26 Oct 2022 12:06:37 +0300 [thread overview]
Message-ID: <Y1j4nX3zvIXXx+ab@unreal> (raw)
In-Reply-To: <20221025184254.1717982-1-kuba@kernel.org>
On Tue, Oct 25, 2022 at 11:42:54AM -0700, Jakub Kicinski wrote:
> The git history for this driver seems to be completely
> automated / tree wide changes. I can't find any boards
> or systems which would use this chip. Google search
> shows pictures of towel warmers and no networking products.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: tsbogend@alpha.franken.de
> CC: mpe@ellerman.id.au
> CC: npiggin@gmail.com
> CC: christophe.leroy@csgroup.eu
> CC: lukas.bulwahn@gmail.com
> CC: arnd@arndb.de
> CC: stephen@networkplumber.org
> CC: shayagr@amazon.com
> CC: leon@kernel.org
> CC: mw@semihalf.com
> CC: petrm@nvidia.com
> CC: wsa+renesas@sang-engineering.com
> CC: linux-mips@vger.kernel.org
> CC: linuxppc-dev@lists.ozlabs.org
> ---
> arch/mips/configs/mtx1_defconfig | 1 -
> arch/powerpc/configs/ppc6xx_defconfig | 1 -
> drivers/net/ethernet/Kconfig | 10 -
> drivers/net/ethernet/Makefile | 1 -
> drivers/net/ethernet/fealnx.c | 1953 -------------------------
> 5 files changed, 1966 deletions(-)
> delete mode 100644 drivers/net/ethernet/fealnx.c
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2022-10-26 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 18:42 [PATCH net-next] eth: fealnx: delete the driver for Myson MTD-800 Jakub Kicinski
2022-10-26 9:06 ` Leon Romanovsky [this message]
2022-10-27 11:40 ` 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=Y1j4nX3zvIXXx+ab@unreal \
--to=leon@kernel.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=petrm@nvidia.com \
--cc=shayagr@amazon.com \
--cc=stephen@networkplumber.org \
--cc=tsbogend@alpha.franken.de \
--cc=wsa+renesas@sang-engineering.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).