patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ankur Dwivedi <adwivedi@marvell.com>, stable@dpdk.org
Cc: anoobj@marvell.com, gakhil@marvell.com, ktejasree@marvell.com,
	jerinj@marvell.com, Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH 0/2] add zuc-256 support
Date: Thu, 23 Jun 2022 15:25:12 +0100	[thread overview]
Message-ID: <200aaa72-bb4e-aca2-8eb7-9e729ad26780@redhat.com> (raw)
In-Reply-To: <20220603111823.311-1-adwivedi@marvell.com>

On 03/06/2022 12:18, Ankur Dwivedi wrote:
> Adds support for zuc-256 cipher in cnxk crypto PMD.
> 
> Ankur Dwivedi (2):
>    common/cnxk: swap zuc-256 key
>    crypto/cnxk: swap zuc-256 iv
> 
>   drivers/common/cnxk/roc_se.c  |  7 +++++--
>   drivers/common/cnxk/roc_se.h  | 22 ++++++++++++++++++++++
>   drivers/crypto/cnxk/cnxk_se.h | 24 +++++++++++++-----------
>   3 files changed, 40 insertions(+), 13 deletions(-)
> 

Hi Ankur,

These patches were missed because they didn't have the branch(es) they 
are requested for in the subject e.g. [PATCH 21.11]. See [0] below.

They are also missing DPDK main branch commit references and Fixes: 
tags. It is not clear from the commit messages if they are fixing 
something that was incorrectly implemented or they are adding a new 
feature. Please check [1] for info on what is backported to stable branches.

[0] 
http://doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases

[1] 
http://doc.dpdk.org/guides/contributing/stable.html#what-changes-should-be-backported

thanks,
Kevin.


  parent reply	other threads:[~2022-06-23 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 11:18 Ankur Dwivedi
2022-06-03 11:18 ` [PATCH 1/2] common/cnxk: swap zuc-256 key Ankur Dwivedi
2022-06-03 11:18 ` [PATCH 2/2] crypto/cnxk: swap zuc-256 iv Ankur Dwivedi
2022-06-23 14:25 ` Kevin Traynor [this message]
2022-06-23 14:42   ` [EXT] Re: [PATCH 0/2] add zuc-256 support Ankur Dwivedi

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=200aaa72-bb4e-aca2-8eb7-9e729ad26780@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=bluca@debian.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=ktejasree@marvell.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).