patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Joel Kavanagh <joel.kavanagh@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>, Kai Ji <kai.ji@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	Ciara Power <ciara.power@intel.com>,
	Fan Zhang <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Brian Dooley <brian.dooley@intel.com>
Subject: RE: [EXTERNAL] [PATCH v2 1/4] crypto/aesni_mb: fix typo in error message
Date: Thu, 18 Jul 2024 15:42:47 +0000	[thread overview]
Message-ID: <CO6PR18MB4484DC2332A7B667F2BC0B3BD8AC2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240717154908.2281023-2-joel.kavanagh@intel.com>

> Subject: [EXTERNAL] [PATCH v2 1/4] crypto/aesni_mb: fix typo in error message
> 
> This patch fixes a typo in the log message for error allocation.
> The typo incorrectly spelled 'allocating' as 'allocationg' in the
> log message for error allocation.
> 
> Fixes: f9dfb59edbcc ("crypto/ipsec_mb: support remaining SGL")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Joel Kavanagh <joel.kavanagh@intel.com>
> Acked-by: Brian Dooley <brian.dooley@intel.com>
Series Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto

Thanks for the fixes.

  reply	other threads:[~2024-07-18 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 13:14 [PATCH v1] " Joel Kavanagh
2024-07-12 14:32 ` Dooley, Brian
2024-07-17 15:49 ` [PATCH v2 0/4] Fix spelling mistakes Joel Kavanagh
2024-07-17 15:49   ` [PATCH v2 1/4] crypto/aesni_mb: fix typo in error message Joel Kavanagh
2024-07-18 15:42     ` Akhil Goyal [this message]
2024-07-17 15:49   ` [PATCH v2 2/4] app/test: fix typo in error message allocation Joel Kavanagh
2024-07-17 15:49   ` [PATCH v2 3/4] crypto/qat: fix typo in log message Joel Kavanagh
2024-07-17 15:49   ` [PATCH v2 4/4] doc: fix typo in l2fwd-crypto guide Joel Kavanagh

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=CO6PR18MB4484DC2332A7B667F2BC0B3BD8AC2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=joel.kavanagh@intel.com \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).