patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Luca Boccassi <bluca@debian.org>, Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: RE: [PATCH 21.11] Revert "crypto/ipsec_mb: fix length and offset settings"
Date: Mon, 21 Mar 2022 19:58:10 +0000	[thread overview]
Message-ID: <DM8PR11MB55910D9E7DEFABCAC5F09DF684169@DM8PR11MB5591.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMw=ZnQzcQhy=Ns9Y58diOUbfALXd8PhYTxabWrwAQ+weZTu9Q@mail.gmail.com>

Hi Kevin,

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Monday, March 21, 2022 7:13 PM
> To: Kevin Traynor <ktraynor@redhat.com>
> Cc: dpdk stable <stable@dpdk.org>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: Re: [PATCH 21.11] Revert "crypto/ipsec_mb: fix length and offset
> settings"
> 
> On Mon, 21 Mar 2022 at 15:35, Kevin Traynor <ktraynor@redhat.com> wrote:
> >
> > This reverts commit daf06c45e8576d8a2a86455e33e2bc4574f8f8b4.
> >
> > As noted [0] reverting this commit because it is reported to introduce
> > a regression [1] and there seems to be some issues [2] with the fix.
> >
> > [0]
> > http://inbox.dpdk.org/stable/3a9ab8af-0a11-248d-24e3-37c7bde7b850@redh
> > at.com/ [1]
> >
> http://inbox.dpdk.org/stable/DM8PR11MB559167EBA31F8DFEEDE9B51584099
> @DM
> > 8PR11MB5591.namprd11.prod.outlook.com/
> > [2]
> >
> http://inbox.dpdk.org/stable/f9030407a47a8554b2c09426c5bc40049647db2d.
> > camel@debian.org/
> >
> > Fixes: daf06c45e857 ("crypto/ipsec_mb: fix length and offset
> > settings")
> >
> > Cc: pablo.de.lara.guarch@intel.com
> > Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> > ---
> >  drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 93
> > ++++++++++----------------
> >  1 file changed, 36 insertions(+), 57 deletions(-)
> 
> Acked-by: Luca Boccassi <bluca@debian.org>

Could you hold this revert for the moment? I think the patch is OK and it's a matter of fixing
the system environment.

Thanks,
Pablo

      reply	other threads:[~2022-03-21 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 15:35 Kevin Traynor
2022-03-21 19:12 ` Luca Boccassi
2022-03-21 19:58   ` De Lara Guarch, Pablo [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=DM8PR11MB55910D9E7DEFABCAC5F09DF684169@DM8PR11MB5591.namprd11.prod.outlook.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=bluca@debian.org \
    --cc=ktraynor@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).