From: "Frank Wunderlich (linux)" <linux@fw-web.de>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
netdev@vger.kernel.org, Sean Wang <sean.wang@mediatek.com>,
Daniel Golle <daniel@makrotopia.org>,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
linux-mediatek@lists.infradead.org,
Simon Horman <horms@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH v2] net: ethernet: mtk_eth_soc: support named IRQs
Date: Sun, 15 Jun 2025 14:02:20 +0200 [thread overview]
Message-ID: <ed6cd7a2e489e89352322f77af1ddd89@fw-web.de> (raw)
In-Reply-To: <aE6cyHC39IV27PcF@lore-desk>
Am 2025-06-15 12:13, schrieb Lorenzo Bianconi:
>> Am 2025-06-15 10:57, schrieb Lorenzo Bianconi:
>> > > From: Frank Wunderlich <frank-w@public-files.de>
>> > >
>> > Hi Frank,
>> >
>> > I guess my comments on v1 apply even in v2. Can you please take a look?
>
> sure
:)
>> Am 2025-06-15 10:57, schrieb Lorenzo Bianconi:
>> > > From: Frank Wunderlich <frank-w@public-files.de>
> I am fine to have it in a separate patch but I would prefer to have
> this patch
> in the same series, I think it is more clear.
I added changes for your and daniels comments to my repo (top 2
commits):
https://github.com/frank-w/BPI-Router-Linux/commits/6.16-mt7988upstream/
i would squash daniels suggestions in this patch here (MAX without __
and fixed
value of 3 to use for the loop - i guess this was intended for this
purpose) and
then the change for index in second patch.
>> > Same here, if you are not listing them in the device tree, you can
>> > remove them
>> > in the driver too (and adjust the code to keep the backward
>> > compatibility).
i plan to use named IRQs on mt7988 without the reserved ones (only rx+tx
+ RSS IRQs),
and loading not index based.
>> afaik i have no SHARED_INT board (only mt7621, mt7628) so changing the
>> index-logic will require testing on such boards too.
>
> I think the change will not heavily impact SHARED_INT devices.
I hope so ;)
> Regards,
> Lorenzo
regards Frank
next prev parent reply other threads:[~2025-06-15 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 8:45 [PATCH v2] net: ethernet: mtk_eth_soc: support named IRQs Frank Wunderlich
2025-06-15 8:57 ` Lorenzo Bianconi
2025-06-15 9:54 ` Frank Wunderlich (linux)
2025-06-15 10:13 ` Lorenzo Bianconi
2025-06-15 12:02 ` Frank Wunderlich (linux) [this message]
2025-06-15 9:26 ` Daniel Golle
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=ed6cd7a2e489e89352322f77af1ddd89@fw-web.de \
--to=linux@fw-web.de \
--cc=andrew+netdev@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--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@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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