From: Anton Blanchard <anton@samba.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Work around for enabling CONFIG_CMDLINE on ppc64le
Date: Thu, 22 Sep 2016 20:47:21 +1000 [thread overview]
Message-ID: <20160922204721.1447f2d5@kryten> (raw)
In-Reply-To: <87d1jw8cba.fsf@concordia.ellerman.id.au>
Hi,
> But I can't merge that patch.
>
> Our options are one or both of:
> - get GCC fixed and backport the fix to the compilers we care about.
> - blacklist the broken compiler versions.
>
> Is there a GCC bug filed for this?
Likely: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709
We need confirmation this patch fixes the 6.x issue too and that we need
a backport.
Anton
next prev parent reply other threads:[~2016-09-22 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 6:20 [PATCH] Work around for enabling CONFIG_CMDLINE on ppc64le Akshay Adiga
2016-09-22 10:21 ` Michael Ellerman
2016-09-22 10:47 ` Anton Blanchard [this message]
2016-09-23 4:15 ` Akshay Adiga
2016-09-27 17:54 ` Akshay Adiga
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=20160922204721.1447f2d5@kryten \
--to=anton@samba.org \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).