patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Gagandeep Singh <g.singh@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH 1/2] common/dpaax: remove dead code
Date: Sat, 16 Apr 2022 19:36:16 +0000	[thread overview]
Message-ID: <CO6PR18MB44848185CFCFC108D3498F17D8F19@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220317085558.2575554-1-g.singh@nxp.com>

> This patch remove structural and logical dead code from
> caamflib.
> 
> coverity issues: 375251 375258 375261 375267 375269 375285 373161
> 		 375249 375257
> 
> Fixes: 6127fff842a7 ("common/dpaax: remove outdated caamflib code")
> Fixes: 81eb760d2207 ("common/dpaax/caamflib: remove some inline keys")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
Series Applied to dpdk-next-crypto

Thanks.

      parent reply	other threads:[~2022-04-16 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  8:55 Gagandeep Singh
2022-03-17  8:55 ` [PATCH 2/2] crypto/dpaa_sec: fix digest size Gagandeep Singh
2022-04-16 19:36 ` Akhil Goyal [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=CO6PR18MB44848185CFCFC108D3498F17D8F19@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).