From: Andrew Morton <akpm@linux-foundation.org>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Greg KH <greg@kroah.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: [PATCH] kernel: add support for gcc 5
Date: Thu, 4 Sep 2014 14:25:29 -0700 [thread overview]
Message-ID: <20140904142529.860f4dc4514def7fb7a9d365@linux-foundation.org> (raw)
In-Reply-To: <CAFLxGvx0Os=qJP8XSpCvj17SNNk6YA1bNZoQsVO3CksgfFbxfQ@mail.gmail.com>
On Thu, 4 Sep 2014 23:19:34 +0200 Richard Weinberger <richard.weinberger@gmail.com> wrote:
> On Thu, Sep 4, 2014 at 11:12 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > On Thu, 4 Sep 2014 11:37:19 -0400 Sasha Levin <sasha.levin@oracle.com> wrote:
> >
> >> We're missing include/linux/compiler-gcc5.h which is required now
> >> because gcc branched off to v5 in trunk.
> >>
> >> Just copy the relevant bits out of include/linux/compiler-gcc4.h,
> >> no new code is added as of now.
> >>
> >> This fixes a build error when using gcc 5.
> >
> > I think I'll stick a cc:stable on this one, as people will presumably
> > wish to compile older kernels with newer gcc's at some time in the
> > future.
>
> CC'ing Hannes, he sent a much simpler gcc5 patch a few days ago.
> https://lkml.org/lkml/2014/8/26/710
That approach won't last for long - as soon as we add some
gcc5-specific thing, we'll need a new file.
Let history be a guide:
diff -u include/linux/compiler-gcc3.h include/linux/compiler-gcc4.h
next prev parent reply other threads:[~2014-09-04 21:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 15:37 Sasha Levin
2014-09-04 21:12 ` Andrew Morton
2014-09-04 21:19 ` Richard Weinberger
2014-09-04 21:25 ` Andrew Morton [this message]
2014-09-04 21:38 ` Sasha Levin
2014-09-05 15:04 ` H. Peter Anvin
2014-09-04 21:25 ` Aaro Koskinen
2014-09-04 21:32 ` Sasha Levin
2014-09-04 22:43 ` Hannes Frederic Sowa
2014-09-04 23:47 ` Joe Perches
2014-09-05 3:37 ` Sasha Levin
2014-09-05 3:58 ` Joe Perches
2014-09-05 4:08 ` Hannes Frederic Sowa
2014-09-05 14:44 ` Sasha Levin
2014-09-05 20:39 ` [PATCH] gcc: clamp gcc version to most highest specific header version available Hannes Frederic Sowa
2014-09-05 21:09 ` Joe Perches
2014-09-05 22:38 ` Hannes Frederic Sowa
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=20140904142529.860f4dc4514def7fb7a9d365@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®