From: Frank Wunderlich <linux@fw-web.de>
To: linux-mediatek@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
Felix Fietkau <nbd@nbd.name>, John Crispin <john@phrozen.org>,
Sean Wang <sean.wang@mediatek.com>,
Mark Lee <Mark-MC.Lee@mediatek.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] support mt7623 and ipv6
Date: Mon, 22 Mar 2021 12:21:15 +0100 [thread overview]
Message-ID: <20210322112117.16162-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
Extending functionality of recently sent nftables flow offload.
This Series contains 2 Patches where the second is for RFC, because i cannot test it,
but it is reported by author as working and i should send it
Series depend on HW offload Patches:
https://patchwork.ozlabs.org/project/netfilter-devel/list/?series=233310&archive=both&state=*
Frank Wunderlich (2):
net: mediatek: add flow offload for mt7623
[RFC] net: ethernet: mtk_eth_soc: add ipv6 flow offload support
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 1 +
.../net/ethernet/mediatek/mtk_ppe_offload.c | 55 +++++++++++++++++++
2 files changed, 56 insertions(+)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-22 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 11:21 Frank Wunderlich [this message]
2021-03-22 11:21 ` [PATCH 1/2] net: mediatek: add flow offload for mt7623 Frank Wunderlich
2021-03-22 11:21 ` [PATCH 2/2] [RFC] net: ethernet: mtk_eth_soc: add ipv6 flow offload support Frank Wunderlich
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=20210322112117.16162-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=Mark-MC.Lee@mediatek.com \
--cc=davem@davemloft.net \
--cc=frank-w@public-files.de \
--cc=john@phrozen.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=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).