From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
michael.chan@broadcom.com, kuba@kernel.org, martin.lau@linux.dev,
kernel-team@meta.com
Subject: Re: [PATCH net-next v3 0/2] bnxt_en: ethtool: Improve wildcard l4proto on ip4/ip6 ntuple rules
Date: Thu, 07 Nov 2024 02:00:38 +0000 [thread overview]
Message-ID: <173094483824.1489169.3032891223925266977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1730778566.git.dxu@dxuuu.xyz>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 4 Nov 2024 21:13:18 -0700 you wrote:
> This patchset improves wildcarding over l4proto on ip4 and ip6 nutple
> rules. Previous support required setting l4proto explicitly to 0xFF if
> you wanted wildcard, which ethtool (naturally) did not do. For example,
> this command would fail with -EOPNOSUPP:
>
> ethtool -N eth0 flow-type ip6 dst-ip $IP6 context 1
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] bnxt_en: ethtool: Remove ip4/ip6 ntuple support for IPPROTO_RAW
https://git.kernel.org/netdev/net-next/c/050eb2cebb9e
- [net-next,v3,2/2] bnxt_en: ethtool: Support unset l4proto on ip4/ip6 ntuple rules
https://git.kernel.org/netdev/net-next/c/5f143efd3804
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-07 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 4:13 Daniel Xu
2024-11-05 4:13 ` [PATCH net-next v3 1/2] bnxt_en: ethtool: Remove ip4/ip6 ntuple support for IPPROTO_RAW Daniel Xu
2024-11-05 17:36 ` Michael Chan
2024-11-05 4:13 ` [PATCH net-next v3 2/2] bnxt_en: ethtool: Support unset l4proto on ip4/ip6 ntuple rules Daniel Xu
2024-11-05 17:50 ` Michael Chan
2024-11-07 2:00 ` patchwork-bot+netdevbpf [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=173094483824.1489169.3032891223925266977.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®