From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] 19.11 - dependencies of 22629f05 "crypto/dpaa_sec: affine the thread portal affinity" not fulfilled
Date: Tue, 1 Jun 2021 09:12:45 +0200 [thread overview]
Message-ID: <CAATJJ0LBqwJTqgdJCgznBLi1dgNCA0nxZM1zCpmGi1vohP==mQ@mail.gmail.com> (raw)
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
next reply other threads:[~2021-06-01 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:12 Christian Ehrhardt [this message]
2021-06-02 15:04 ` Hemant Agrawal
2021-06-03 5:45 ` Christian Ehrhardt
2021-06-03 12:20 ` Hemant Agrawal
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='CAATJJ0LBqwJTqgdJCgznBLi1dgNCA0nxZM1zCpmGi1vohP==mQ@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=hemant.agrawal@nxp.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).