From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Mike Galbraith <efault@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Rik van Riel <riel@surriel.com>
Subject: Re: Build failures with gcc 4.5 and older
Date: Mon, 20 Aug 2018 11:34:28 -0700 [thread overview]
Message-ID: <CA+55aFzTPCoarqD7=2NFFvZjmZQjr=FhTWMFfLm+UfaF+M_ixg@mail.gmail.com> (raw)
In-Reply-To: <20180820174655.75739-1-ndesaulniers@google.com>
On Mon, Aug 20, 2018 at 10:46 AM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> I think we should take Joe's patch.
I'll happily take Joe's patch and get the whole "ancient gcc versions"
issue behind us.
We'll come back to it in a few years when 4.6 is ancient too, but for
now we have no pressing need not to support it.
Joe - proper commit message and sign-off?
Linus
next prev parent reply other threads:[~2018-08-20 18:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 17:09 Build failures with gcc 4.5 and older Guenter Roeck
2018-08-14 17:20 ` Linus Torvalds
2018-08-14 17:36 ` Guenter Roeck
2018-08-14 20:19 ` Tony Luck
2018-08-15 16:09 ` Tony Luck
2018-08-15 16:34 ` Linus Torvalds
2018-08-16 0:27 ` Guenter Roeck
2018-08-15 16:49 ` Guenter Roeck
2018-08-14 17:48 ` Joe Perches
2018-08-19 21:23 ` Kees Cook
2018-08-20 17:46 ` Nick Desaulniers
2018-08-20 18:34 ` Linus Torvalds [this message]
2018-08-14 21:36 ` Andrew Morton
2018-08-14 22:15 ` Guenter Roeck
2018-08-14 23:02 ` Andrew Morton
2018-08-14 23:20 ` Linus Torvalds
2018-08-15 1:02 ` Guenter Roeck
2018-08-20 14:53 ` Thomas Gleixner
2018-08-20 16:00 ` Arnd Bergmann
2018-08-15 12:40 ` David Laight
2018-08-15 15:44 ` Linus Torvalds
2018-08-15 16:18 ` David Laight
2018-08-15 16:33 ` Linus Torvalds
2018-08-16 9:17 ` David Laight
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='CA+55aFzTPCoarqD7=2NFFvZjmZQjr=FhTWMFfLm+UfaF+M_ixg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=efault@gmx.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ndesaulniers@google.com \
--cc=riel@surriel.com \
/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).