patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	dpdk stable <stable@dpdk.org>,
	Kevin Traynor <ktraynor@redhat.com>,
	Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then?
Date: Mon, 28 Jun 2021 10:13:02 +0100	[thread overview]
Message-ID: <205f243e1ed6df6d5b17817e6af4a91f0705fb56.camel@debian.org> (raw)
In-Reply-To: <CAATJJ0+LKEsm=ucC9y3W4JEmrEDO=-VzxtZneBsjjvF8mTC=ng@mail.gmail.com>

On Mon, 2021-06-28 at 09:34 +0200, Christian Ehrhardt wrote:
> 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

Can't remember the details about this particular one, but I think
several fixes were backported for the -fno-common issue in 19.11

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2021-06-28  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28  7:34 Christian Ehrhardt
2021-06-28  9:13 ` Luca Boccassi [this message]
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=205f243e1ed6df6d5b17817e6af4a91f0705fb56.camel@debian.org \
    --to=bluca@debian.org \
    --cc=akhil.goyal@nxp.com \
    --cc=christian.ehrhardt@canonical.com \
    --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).