From: Andi Kleen <andi@firstfloor.org>
To: Joe Perches <joe@perches.com>
Cc: Andi Kleen <andi@firstfloor.org>, Michal Marek <mmarek@suse.cz>,
akpm@linux-foundation.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH] Support gcc 6 for building
Date: Thu, 16 Apr 2015 18:29:38 +0200 [thread overview]
Message-ID: <20150416162938.GU2366@two.firstfloor.org> (raw)
In-Reply-To: <1429201390.2850.54.camel@perches.com>
> As compiler-gcc3.h is trivial, what about integrating
> the whole thing into a single file and get rid of the
> compiler-gcc<version>.h files?
I think that's the right thing to do yes.
-Andi
next prev parent reply other threads:[~2015-04-16 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 19:45 [PATCH] Support gcc 6 for building Andi Kleen
2015-04-16 3:04 ` Segher Boessenkool
2015-04-16 7:57 ` Michal Marek
2015-04-16 15:56 ` Andi Kleen
2015-04-16 16:23 ` Joe Perches
2015-04-16 16:29 ` Andi Kleen [this message]
2015-04-16 20:31 ` [PATCH 0/2] Integrate compiler-gcc[345].h files into compiler-gcc.h Joe Perches
2015-04-16 20:31 ` [PATCH 1/2] compiler-gcc.h: Neatening Joe Perches
2015-04-16 20:44 ` Joe Perches
2015-04-16 20:31 ` [PATCH 2/2] compiler-gcc: Integrate the various compiler-gcc[345].h files Joe Perches
2015-04-20 21:17 ` [PATCH 0/2] Integrate compiler-gcc[345].h files into compiler-gcc.h Andrew Morton
2015-04-20 21:24 ` Andi Kleen
2015-04-16 20:13 ` [PATCH] Support gcc 6 for building Michal Marek
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=20150416162938.GU2366@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=segher@kernel.crashing.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