Devicetree
 help / color / mirror / Atom feed
From: David Yang <mmyangfl@gmail.com>
To: robh@kernel.org, kuba@kernel.org
Cc: andrew+netdev@lunn.ch, conor+dt@kernel.org, davem@davemloft.net,
	devicetree@vger.kernel.org, edumazet@kernel.org,
	hkallweit1@gmail.com, krzk+dt@kernel.org,
	linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
	netdev@vger.kernel.org, p.zabel@pengutronix.de,
	pabeni@redhat.com, shaojijie@huawei.com, shenjian15@huawei.com,
	David Yang <mmyangfl@gmail.com>
Subject: Re: [PATCH] net: hisilicon: Remove orphan femac driver
Date: Fri, 20 Nov 2026 11:51:27 +0800	[thread overview]
Message-ID: <20261120035127.1383109-1-mmyangfl@gmail.com> (raw)
In-Reply-To: <20261104145038.946918-1-robh@kernel.org>

Hi,

Sorry to see this, but please reconsider removing this driver. It is in
active use here and is about to get its first upstream SoC users.

Two HiSTB SoC families that we are bringing up on mainline use this
MAC as their Ethernet interface: Hi3798MV100 and Hi3798MV200H. Two fixes
from us, both found and verified on this hardware, were merged into the
net tree in the weeks just before this removal, so this is not dead code
on our side:

  444889dfa27b net: hisilicon: hisi_femac: Move setting of netops to
               fix crash
  d54b21d82430 net: hisilicon: hisi_femac: Stop the receiver before
               releasing the RX ring

Beyond femac, the HiSTB platform push is active on our side: a dmaengine
series for the Hi3798MV100 PL080 variant is under review (v2 [1]), and
more HiSTB platform work is in the pipeline.

We are also willing to maintain this driver going forward. If you would
rather not undo the removal, tell us the shape you prefer and we will do
that instead.

Thanks

[1] https://lore.kernel.org/r/20261106072602.77560-1-mmyangfl@gmail.com/

      parent reply	other threads:[~2026-11-20  3:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 14:50 [PATCH net-next] net: hisilicon: Remove orphan femac driver Rob Herring (Arm)
2026-11-04 14:56 ` Krzysztof Kozlowski
2026-11-09  2:27 ` Jijie Shao
2026-11-10  2:55 ` patchwork-bot+netdevbpf
2026-11-20  3:51 ` David Yang [this message]

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=20261120035127.1383109-1-mmyangfl@gmail.com \
    --to=mmyangfl@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.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