From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] compiler-gcc: require gcc 4.8 for powerpc __builtin_bswap16()
Date: Mon, 9 May 2016 18:31:02 +1000 [thread overview]
Message-ID: <20160509183102.45d8dbe9@canb.auug.org.au> (raw)
In-Reply-To: <CA+icZUWuybX42vW=ADLT_b+_P87DGjtcA3nXGpV+gq5LtkB3eA@mail.gmail.com>
Hi Sedat,
On Mon, 9 May 2016 07:39:24 +0200 Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
> On 5/9/16, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > And since "byteswap: try to avoid __builtin_constant_p gcc bug" is not
> > in Linus' tree, hopefully we can have this fix applied soon.
>
> FYI, this patch is in Linus tree (v4.6-rc7 has it).
Yes, the "not" was a typo.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-05-09 8:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 4:58 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2016-05-06 5:44 ` Andrew Morton
2016-05-06 6:09 ` Stephen Rothwell
2016-05-06 6:55 ` Michael Ellerman
2016-05-06 14:22 ` [PATCH] compiler-gcc: require gcc 4.8 for powerpc __builtin_bswap16() Josh Poimboeuf
2016-05-09 0:59 ` Stephen Rothwell
2016-05-09 5:39 ` Sedat Dilek
2016-05-09 8:31 ` Stephen Rothwell [this message]
2016-05-09 6:33 ` Stephen Rothwell
2016-05-09 9:34 ` Michael Ellerman
2016-05-09 10:16 ` Arnd Bergmann
2016-05-09 10:36 ` Stephen Rothwell
2016-06-15 9:33 ` linux-next: build failure after merge of the akpm-current tree Paul Bolle
2016-06-15 14:03 ` Josh Poimboeuf
2016-06-15 21:12 ` Paul Bolle
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=20160509183102.45d8dbe9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.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).