From: Jakub Kicinski <kuba@kernel•org>
To: Jacob Keller <jacob.e.keller@intel•com>
Cc: Simon Horman <horms@kernel•org>, Jiri Pirko <jiri@resnulli•us>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
"Paolo Abeni" <pabeni@redhat•com>,
Jonathan Corbet <corbet@lwn•net>,
Tony Nguyen <anthony.l.nguyen@intel•com>,
Przemek Kitszel <przemyslaw.kitszel@intel•com>,
Andrew Lunn <andrew+netdev@lunn•ch>,
Alexander Lobakin <aleksander.lobakin@intel•com>,
<netdev@vger•kernel.org>, <linux-doc@vger•kernel.org>,
<linux-kernel@vger•kernel.org>, Dan Nowlin <dan.nowlin@intel•com>,
Qi Zhang <qi.z.zhang@intel•com>, Jie Wang <jie1x.wang@intel•com>,
Junfeng Guo <junfeng.guo@intel•com>,
"Jedrzej Jagielski" <jedrzej.jagielski@intel•com>,
Aleksandr Loktionov <aleksandr.loktionov@intel•com>,
Rafal Romanowski <rafal.romanowski@intel•com>
Subject: Re: [PATCH net-next 06/14] ice: Extend PTYPE bitmap coverage for GTP encapsulated flows
Date: Thu, 16 Oct 2025 16:56:48 -0700 [thread overview]
Message-ID: <20251016165648.2f53e1fc@kernel.org> (raw)
In-Reply-To: <902dab41-51f0-4e01-8149-921fb80db23d@intel.com>
On Thu, 16 Oct 2025 14:37:53 -0700 Jacob Keller wrote:
> What version of git are you using? I'm using git v2.51.0 Perhaps this
> isn't a b4 or git issue but some other tooling that is causing an issue
> (patchwork?).
Looks like patchwork, it serves us:
https://patchwork.kernel.org/project/netdevbpf/patch/20251015-jk-iwl-next-2025-10-15-v1-6-79c70b9ddab8@intel.com/mbox
which has the -- "corrected" to ---
Doesn't matter all that much cause there are also kdoc issues on
patches 4 and 5. Obligatory advertisement:
https://github.com/linux-netdev/nipa?tab=readme-ov-file#running-locally
--
pw-bot: cr
next prev parent reply other threads:[~2025-10-16 23:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 19:31 [PATCH net-next 00/14] Intel Wired LAN Driver Updates 2025-10-15 (ice, iavf, ixgbe, i40e, e1000e) Jacob Keller
2025-10-15 19:31 ` [PATCH net-next 01/14] devlink: Add new "max_mac_per_vf" generic device param Jacob Keller
2025-10-15 19:31 ` [PATCH net-next 02/14] i40e: support generic devlink param "max_mac_per_vf" Jacob Keller
2025-10-15 19:31 ` [PATCH net-next 03/14] ice: add flow parsing for GTP and new protocol field support Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 04/14] ice: add virtchnl and VF context support for GTP RSS Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 05/14] ice: improve TCAM priority handling for RSS profiles Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 06/14] ice: Extend PTYPE bitmap coverage for GTP encapsulated flows Jacob Keller
2025-10-16 12:21 ` Simon Horman
2025-10-16 17:20 ` Jacob Keller
2025-10-16 19:03 ` Simon Horman
2025-10-16 21:37 ` Jacob Keller
2025-10-16 23:56 ` Jakub Kicinski [this message]
2025-10-17 0:31 ` Jacob Keller
2025-10-17 6:10 ` Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 07/14] iavf: add RSS support for GTP protocol via ethtool Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 08/14] net: docs: add missing features that can have stats Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 09/14] ice: implement ethtool standard stats Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 10/14] ice: add tracking of good transmit timestamps Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 11/14] ice: implement transmit hardware timestamp statistics Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 12/14] ice: refactor to use helpers Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 13/14] ixgbe: preserve RSS indirection table across admin down/up Jacob Keller
2025-10-15 19:32 ` [PATCH net-next 14/14] e1000e: Introduce private flag to disable K1 Jacob Keller
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=20251016165648.2f53e1fc@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=aleksander.lobakin@intel$(echo .)com \
--cc=aleksandr.loktionov@intel$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=dan.nowlin@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jedrzej.jagielski@intel$(echo .)com \
--cc=jie1x.wang@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=junfeng.guo@intel$(echo .)com \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=qi.z.zhang@intel$(echo .)com \
--cc=rafal.romanowski@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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