From: Luca Boccassi <bluca@debian.org>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>
Cc: Kevin Traynor <ktraynor@redhat.com>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [19.11][20.11][21.11] ppc64 fixes backport
Date: Wed, 6 Jul 2022 19:53:07 +0100 [thread overview]
Message-ID: <CAMw=ZnR6Ef9x=hc1iT+8Eu=sn8gfahAY3+c4y0ePtH5R6mcVoA@mail.gmail.com> (raw)
In-Reply-To: <BN9PR12MB5366E0E8FD5257498BB76449A1BB9@BN9PR12MB5366.namprd12.prod.outlook.com>
On Wed, 29 Jun 2022 at 14:40, Xueming(Steven) Li <xuemingl@nvidia.com> wrote:
>
> Hi LTS maintainers,
>
> Confirmed with Thomas, mlx5 PMD needs the following patches to compile with the upstream rdma-core lib.
>
> 2022-05-25 2022-06-01 b251bb7630 eal/ppc: undefine AltiVec keyword vector @Thomas Monjalon
> 2022-05-03 2022-05-25 64fcadeac0 avoid AltiVec keyword vector @Thomas Monjalon
>
> I tried to backport to 20.11.6 LTS, cherry-pick works without conflicts.
>
> Best Regards,
> Xueming Li
Hi,
This patch:
2022-05-25 2022-06-01 b251bb7630 eal/ppc: undefine AltiVec keyword
vector @Thomas Monjalon
Looks like an incompatible change? Commit message says so too:
"This is a compatibility breakage for applications which were using
the keyword "vector" for its AltiVec meaning."
The first one looks like but I don't think we should pick up the
second one for the LTS branches?
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2022-07-06 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 13:40 Xueming(Steven) Li
2022-07-06 18:53 ` Luca Boccassi [this message]
2022-07-07 6:51 ` Thomas Monjalon
2022-07-07 7:44 ` Christian Ehrhardt
2022-07-07 8:21 ` Thomas Monjalon
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='CAMw=ZnR6Ef9x=hc1iT+8Eu=sn8gfahAY3+c4y0ePtH5R6mcVoA@mail.gmail.com' \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.com \
/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).