From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: dpdk stable <stable@dpdk.org>, Luca Boccassi <bluca@debian.org>,
Kevin Traynor <ktraynor@redhat.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then?
Date: Mon, 28 Jun 2021 09:34:57 +0200 [thread overview]
Message-ID: <CAATJJ0+LKEsm=ucC9y3W4JEmrEDO=-VzxtZneBsjjvF8mTC=ng@mail.gmail.com> (raw)
Hi,
there is an old patch [1] which back then was not considered/taken
into 19.11 series.
This is now breaking Clang build [2].
Since you were the Author/Maintainers back then I wanted to ask if
there was a reason to not pick it? If it should be picked now and if
there are any special things to consider for a backport?
Chiming in/subscribing to the bug would also be appreciated.
[1]: https://github.com/DPDK/dpdk/commit/eef9e0412a84cddf8944379ed4995314b4369370
[2]: https://bugs.dpdk.org/show_bug.cgi?id=733#c6
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next reply other threads:[~2021-06-28 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 7:34 Christian Ehrhardt [this message]
2021-06-28 9:13 ` Luca Boccassi
2021-06-28 9:47 ` Kevin Traynor
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='CAATJJ0+LKEsm=ucC9y3W4JEmrEDO=-VzxtZneBsjjvF8mTC=ng@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=akhil.goyal@nxp.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).