patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdk stable <stable@dpdk.org>, Luca Boccassi <bluca@debian.org>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: Re: [PATCH 21.11] build: suppress rte_crypto_asym_op abi check
Date: Wed, 16 Mar 2022 16:51:15 +0000	[thread overview]
Message-ID: <683da05f-b896-7254-598d-40a196489fc8@redhat.com> (raw)
In-Reply-To: <CAJFAV8yTOm5Gjvyxh+PJsNt3wOAVWdNvkwT9kBQ4UK8zx+rDGA@mail.gmail.com>

On 16/03/2022 16:14, David Marchand wrote:
> On Wed, Mar 16, 2022 at 12:45 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>>
>> Suppress of rte_crypto_asym_op was added in dpdk main branch
>> as part of
>> a678c5d36589 ("cryptodev: add DSA random number k")
>>
>> That is not backported to 21.11 branch, but other commit
>> f092922c3674 ("cryptodev: fix RSA key type name")
>> also needs this suppression.
>>

This caused a failure in UNH CI
https://lab.dpdk.org/results/dashboard/tarballs/19132

>> Add the suppression here.
>>
>> Fixes: f092922c3674 ("cryptodev: fix RSA key type name")
>> Cc: arkadiuszx.kusztal@intel.com
>>
>> Reported-by: https://lab.dpdk.org/results/dashboard/tarballs/19132
> 
> In dpdk history, the Reported-by tag has always been used with people
> names, and not URI.
> It is probably not an issue (except maybe for people doing stats on
> those tags), but I would rather keep this URI as a comment in the
> commitlog.
> 

ok, sure. I changed it to free form in the commit msg as above instead.

>> Reported-by: David Marchand <david.marchand@redhat.com>
>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> 
> The change lgtm,
> 
> Reviewed-by: David Marchand <david.marchand@redhat.com>

Thanks. Applied with changes above.

> 
> 



      reply	other threads:[~2022-03-16 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 11:45 Kevin Traynor
2022-03-16 16:08 ` Kevin Traynor
2022-03-16 16:14 ` David Marchand
2022-03-16 16:51   ` Kevin Traynor [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=683da05f-b896-7254-598d-40a196489fc8@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.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).