DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Nicolau <radu.nicolau@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH v1 0/6] IXGBE IPsec fixes
Date: Tue, 18 Aug 2026 17:14:08 +0100	[thread overview]
Message-ID: <f081ed03-997f-4daa-88fe-ce309eb79591@intel.com> (raw)
In-Reply-To: <cover.1787059137.git.anatoly.burakov@intel.com>


On 18-Aug-26 2:19 PM, Anatoly Burakov wrote:
> Small array of fixes and refactors for IXGBE IPsec implementation.
>
> Anatoly Burakov (6):
>    net/ixgbe: add key length check in IPsec
>    net/ixgbe: remove unnecessary dev pointer
>    net/ixgbe: harmonize return values in IPsec
>    net/ixgbe: get rid of unnecessary malloc in IPsec
>    net/ixgbe: fix missing HW write in IPsec
>    net/ixgbe: refactor IPsec code
>
>   drivers/net/intel/ixgbe/ixgbe_ipsec.c | 355 ++++++++++++--------------
>   drivers/net/intel/ixgbe/ixgbe_ipsec.h |   1 +
>   2 files changed, 161 insertions(+), 195 deletions(-)
Series-acked-by: Radu Nicolau <radu.nicolau@intel.com>

      parent reply	other threads:[~2026-08-18 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 13:19 [PATCH v1 0/6] IXGBE IPsec fixes Anatoly Burakov
2026-08-18 13:19 ` [PATCH v1 1/6] net/ixgbe: add key length check in IPsec Anatoly Burakov
2026-08-18 13:19 ` [PATCH v1 2/6] net/ixgbe: remove unnecessary dev pointer Anatoly Burakov
2026-08-18 13:19 ` [PATCH v1 3/6] net/ixgbe: harmonize return values in IPsec Anatoly Burakov
2026-08-18 13:19 ` [PATCH v1 4/6] net/ixgbe: get rid of unnecessary malloc " Anatoly Burakov
2026-08-18 13:19 ` [PATCH v1 5/6] net/ixgbe: fix missing HW write " Anatoly Burakov
2026-08-18 13:19 ` [PATCH v1 6/6] net/ixgbe: refactor IPsec code Anatoly Burakov
2026-08-18 16:14 ` Radu Nicolau [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=f081ed03-997f-4daa-88fe-ce309eb79591@intel.com \
    --to=radu.nicolau@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.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