From: Jakub Kicinski <kuba@kernel.org>
To: Gavin Li <gavinl@nvidia.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<roopa@nvidia.com>, <eng.alaamohamedsoliman.am@gmail.com>,
<bigeasy@linutronix.de>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <gavi@nvidia.com>,
<roid@nvidia.com>, <maord@nvidia.com>, <saeedm@nvidia.com>
Subject: Re: [PATCH net-next v4 0/4] net/mlx5e: Add GBP VxLAN HW offload support
Date: Tue, 21 Feb 2023 19:36:30 -0800 [thread overview]
Message-ID: <20230221193630.5f210ea5@kernel.org> (raw)
In-Reply-To: <20230222025653.20425-1-gavinl@nvidia.com>
On Wed, 22 Feb 2023 04:56:49 +0200 Gavin Li wrote:
> Patch-1: Remove unused argument from functions.
> Patch-2: Expose helper function vxlan_build_gbp_hdr.
> Patch-3: Add helper function for encap_info_equal for tunnels with options.
> Patch-4: Add HW offloading support for TC flows with VxLAN GBP encap/decap
> in mlx ethernet driver.
# Form letter - net-next is closed
The merge window for v6.3 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after Mar 6th.
RFC patches sent for review only are obviously welcome at any time.
prev parent reply other threads:[~2023-02-22 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 2:56 [PATCH net-next v4 0/4] net/mlx5e: Add GBP VxLAN HW offload support Gavin Li
2023-02-22 2:56 ` [PATCH net-next v4 1/4] vxlan: Remove unused argument from vxlan_build_gbp_hdr( ) and vxlan_build_gpe_hdr( ) Gavin Li
2023-02-22 2:56 ` [PATCH net-next v4 2/4] vxlan: Expose helper vxlan_build_gbp_hdr Gavin Li
2023-02-22 2:56 ` [PATCH net-next v4 3/4] net/mlx5e: Add helper for encap_info_equal for tunnels with options Gavin Li
2023-02-22 2:56 ` [PATCH net-next v4 4/4] net/mlx5e: TC, Add support for VxLAN GBP encap/decap flows offload Gavin Li
2023-02-22 3:36 ` Jakub Kicinski [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=20230221193630.5f210ea5@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eng.alaamohamedsoliman.am@gmail.com \
--cc=gavi@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maord@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=roopa@nvidia.com \
--cc=saeedm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.