From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] 19.11 - dependencies of 22629f05 "crypto/dpaa_sec: affine the thread portal affinity" not fulfilled
Date: Thu, 3 Jun 2021 12:20:06 +0000 [thread overview]
Message-ID: <PAXPR04MB8173E797E578F34F2403E504893C9@PAXPR04MB8173.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAATJJ0J3PMAR246EU-5iRD8iZ-o_V5MThyMNazGUeGvqSHfPrg@mail.gmail.com>
> On Wed, Jun 2, 2021 at 5:04 PM Hemant Agrawal
> <hemant.agrawal@nxp.com> wrote:
> >
> > I will be submitting a patch in next 1-2 days.
>
> Thanks in advance!
>
> I was collecting a few more changes for a 19.11.9-rc2 today, but I do not
> want to tag a release candidate every day.
> So I'm waiting for your changes to show up (or you telling me that it won't be
> backported).
> It would be great if those could be available *tomorrow morning to be able
> to tag rc2 before this week is over.
[Hemant] done.
>
> * = my tomorrow morning so ~23h from the time I sent this email :-)
>
> > - Hemant
> >
> > > -----Original Message-----
> > > From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > > Sent: Tuesday, June 1, 2021 12:43 PM
> > > To: Hemant Agrawal <hemant.agrawal@nxp.com>
> > > Cc: dpdk stable <stable@dpdk.org>
> > > Subject: 19.11 - dependencies of 22629f05 "crypto/dpaa_sec: affine
> > > the thread portal affinity" not fulfilled
> > >
> > > Hi Hemant,
> > > this commit was targeted for the stable releases:
> > >
> > > commit 22629f05f8832358d01872414e0e30c2c81e43d4
> > > Author: Hemant Agrawal <hemant.agrawal@nxp.com>
> > > Date: Mon May 3 14:09:53 2021 +0530
> > >
> > > crypto/dpaa_sec: affine the thread portal affinity
> > >
> > > But prior to 20.08 the following change was not present.
> > >
> > > commit e58722218aa9ad6b527423f8b95e788e6c5a15b7
> > > Author: Rohit Raj <rohit.raj@nxp.com>
> > > Date: Tue Jul 7 14:52:27 2020 +0530
> > >
> > > drivers/dpaa: optimize thread local storage
> > >
> > > That leads to compile errors and seems not trivial to backport as
> > > changes to local storage could have various dependencies and
> > > implications that I might miss.
> > >
> > > If you want the patch applied to 19.11 I'd ask you to have a look
> > > and provide a backport for it that considers all that and is tested.
> > > Otherwise please feel free to just let me know that 19.11 series
> > > will be fine without 22629f05.
> > >
> > > --
> > > Christian Ehrhardt
> > > Staff Engineer, Ubuntu Server
> > > Canonical Ltd
>
>
>
> --
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd
next prev parent reply other threads:[~2021-06-03 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:12 Christian Ehrhardt
2021-06-02 15:04 ` Hemant Agrawal
2021-06-03 5:45 ` Christian Ehrhardt
2021-06-03 12:20 ` Hemant Agrawal [this message]
2021-06-04 5:10 ` Christian Ehrhardt
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=PAXPR04MB8173E797E578F34F2403E504893C9@PAXPR04MB8173.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=christian.ehrhardt@canonical.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).