From: Jakub Kicinski <kuba@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: yangshiji66@outlook.com, netdev@vger.kernel.org, nbd@nbd.name,
lorenzo@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [net PATCH] net: ethernet: mediatek: only enable WED for ARM64 architecture
Date: Wed, 23 Sep 2026 19:41:59 -0700 [thread overview]
Message-ID: <20260923194159.264ca04b@kernel.org> (raw)
In-Reply-To: <179009659284.2160803.2402786454793152027@kernel.org>
On Tue, 22 Sep 2026 17:03:12 +0000 netdev-bot+sashiko@kernel.org wrote:
> Is the Fixes: tag appropriate here? The changelog does not describe a
> defect, only a hardware-scope observation and a prediction:
>
> Currently, only MT7622 and MT798x SoCs support WED features. They
> are all ARM64 platforms. And it is unlikely that MediaTek will
> release a new net chip based on ARM32 architecture in the future.
>
> As far as I can tell nothing misbehaves on 32-bit today.
Not just the fixes tag, the whole commit seems rather pointless.
--
pw-bot: reject
next prev parent reply other threads:[~2026-09-24 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:03 [net PATCH] net: ethernet: mediatek: only enable WED for ARM64 architecture netdev-bot+sashiko
2026-09-24 2:41 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-18 16:38 Shiji Yang
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=20260923194159.264ca04b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yangshiji66@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.