From: "Frank Wunderlich" <frank.wunderlich@linux.dev>
To: "Jakub Kicinski" <kuba@kernel.org>,
"Frank Wunderlich" <frank-w@public-files.de>
Cc: linux@fw-web.de, nbd@nbd.name, sean.wang@mediatek.com,
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@armlinux.org.uk,
daniel@makrotopia.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [RFC net-next v5 0/3] Add RSS and LRO support
Date: Sun, 12 Apr 2026 19:24:30 +0000 [thread overview]
Message-ID: <ee4d27c8bf587a66953d8705ccbaecdffdc66d68@linux.dev> (raw)
In-Reply-To: <20260412075402.2eda04d3@kernel.org>
Am 12. April 2026 um 16:54 schrieb "Jakub Kicinski" <kuba@kernel.org>:
>
> On Sun, 12 Apr 2026 11:57:47 +0000 Frank Wunderlich wrote:
>
> >
> > some time has passed without a single comment, so i just send a friendly reminder ;)
> >
> You have a lot of people in the To:
> Could you clarify who you expect to action these patches?
> Patches are an RFC and I suppose ain't nobody got much comments?
Hi,
imho 11 people are in "To" is not much, but i was told that no comments can mean
"OK so far" so i will send v6 soon rebased on current net-next.
regards Frank
prev parent reply other threads:[~2026-04-12 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 15:12 [RFC net-next v5 0/3] Add RSS and LRO support Frank Wunderlich
2025-12-19 15:12 ` [RFC net-next v5 1/3] net: ethernet: mtk_eth_soc: Add register definitions for RSS and LRO Frank Wunderlich
2025-12-19 15:12 ` [RFC net-next v5 2/3] net: ethernet: mtk_eth_soc: Add RSS support Frank Wunderlich
2025-12-19 15:12 ` [RFC net-next v5 3/3] net: ethernet: mtk_eth_soc: Add LRO support Frank Wunderlich
2026-04-12 11:57 ` Aw: [RFC net-next v5 0/3] Add RSS and " Frank Wunderlich
2026-04-12 14:54 ` Jakub Kicinski
2026-04-12 19:24 ` Frank Wunderlich [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=ee4d27c8bf587a66953d8705ccbaecdffdc66d68@linux.dev \
--to=frank.wunderlich@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frank-w@public-files.de \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linux@fw-web.de \
--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