Hi,
30/08/2018 13:58, Christian Ehrhardt:
> On Thu, Aug 30, 2018 at 12:52 PM Takeshi T Yoshimura <t...@jp.ibm.com>
> wrote:
> > Hi,
> > I could reproduce the issue you reported in 18.08 with my ppc64le box with
> > RedHat 7.5 and GCC4.8.
> > The patch resolved the issue in my environment. Thanks!
>
> I added your test (tanks) and Adrien's extensive review/discussion as tags
> and also addressed a few checkpatch findings.
> V2 is up on the list now ...
>
> > I am a bit newbie in dpdk-dev, but I will try contacting Chao and other
> > IBM guys... Sorry for our slow reply.
>
> Thanks for your participation Takeshi,
> we at least now have had a few replies after Thomas used the superpowers of
> "CPT. CAPSLOCK" \o/.
>
> I also have a call later today to make sure this is brought up inside IBM
> to make sure someone is maintaining it for real.
Summary of the situation:
- I used caps lock on August 30th
- We got replies on the ML in the next 2 days (Alfredo, Chao, Takeshi)
- On September 3rd, Adrien raised a major issue for C++ with the fix v3
http://mails.dpdk.org/archives/dev/2018-September/110733.html
- Another email about a possible GCC fix on September 5th (David Wilder)
- There was a private reply on September 27th, confirming an IBM support
- and nothing else
Nobody at IBM requests to get a compilation fix for ppc64.
And there was no issue raised after 18.11-rc1 release.
I guess it means DPDK is not used on ppc64.
In this case, we should mark the ppc port as unmaintained for 18.11.
OR SHOULD I USE MY CAPS LOCK AGAIN?
