From: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 20.11.8
Date: Thu, 2 Mar 2023 10:18:42 +0000 [thread overview]
Message-ID: <MW4PR11MB59111049D1BC02E18FADA13D87B29@MW4PR11MB5911.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMw=ZnTERUc+19Or1=MkWa_MsFKzomrDe291tkqf+FYDHEKB2g@mail.gmail.com>
Then branch is out of sync
> -----Original Message-----
> From: Luca Boccassi <luca.boccassi@gmail.com>
> Sent: Thursday, March 2, 2023 3:18 PM
> To: Kundapura, Ganapati <ganapati.kundapura@intel.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: Re: please help backporting some patches to stable release 20.11.8
>
> On Wed, 1 Mar 2023 at 16:15, Kundapura, Ganapati
> <ganapati.kundapura@intel.com> wrote:
> >
> > Hi Luca,
> > Below mentioned crypto patches has dependency on below commit
> >
> > commit 2ae84b39ae7b92c6b72f9dc9aa0a4aa2572e10e1
> > Author: Ganapati Kundapura <ganapati.kundapura@intel.com>
> > Date: Thu Feb 10 11:41:16 2022 -0600
> >
> > eventdev/crypto: store operations in circular buffer
> >
> > Move crypto ops to circular buffer to retain crypto
> > ops when cryptodev/eventdev are temporarily full.
> >
> > Signed-off-by: Ganapati Kundapura <ganapati.kundapura@intel.com>
> > Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> >
> > Could you please pull this commit and try applying other patches?
> >
> > Thanks,
> > Ganapati
>
> Hi,
>
> That doesn't apply either, with tons of conflicts.
next prev parent reply other threads:[~2023-03-02 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:42 luca.boccassi
2023-03-01 16:15 ` Kundapura, Ganapati
2023-03-02 9:47 ` Luca Boccassi
2023-03-02 10:18 ` Kundapura, Ganapati [this message]
2023-03-21 9:29 ` lihuisong (C)
2023-03-15 22:49 luca.boccassi
2023-03-21 9:37 ` lihuisong (C)
2023-03-22 0:43 luca.boccassi
2023-03-29 1:05 luca.boccassi
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=MW4PR11MB59111049D1BC02E18FADA13D87B29@MW4PR11MB5911.namprd11.prod.outlook.com \
--to=ganapati.kundapura@intel.com \
--cc=luca.boccassi@gmail.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).