From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Miguel Ojeda <ojeda@kernel.org>, Will Deacon <will@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Joe Perches <joe@perches.com>, Paul Mackerras <paulus@samba.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Tue, 4 May 2021 10:38:32 +0200 [thread overview]
Message-ID: <CANiq72mk84uay--BWOLT4zF12-rat9erohKazB8SpTPoVCTX1A@mail.gmail.com> (raw)
In-Reply-To: <65cda2bb-1b02-6ebc-0ea2-c48927524aa0@codethink.co.uk>
On Tue, May 4, 2021 at 9:57 AM Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>
> Some of us are a bit stuck as either customer refuses to upgrade
> their build infrastructure or has paid for some old but safety
> blessed version of gcc. These often lag years behind the recent
> gcc releases :(
In those scenarios, why do you need to build mainline? Aren't your
customers using longterm or frozen kernels? If they are paying for
certified GCC images, aren't they already paying for supported kernel
images from some vendor too?
I understand where you are coming from -- I have also dealt with
projects/machines running ancient, unsupported software/toolchains for
various reasons; but nobody expected upstream (and in particular the
mainline kernel source) to support them. In the cases I experienced,
those use cases require not touching anything at all, and when the
time came of doing so, everything would be updated at once,
re-certified/validated as needed and frozen again.
Cheers,
Miguel
next prev parent reply other threads:[~2021-05-04 8:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 17:38 ` Christophe Leroy
2021-05-02 2:41 ` Joe Perches
2021-05-02 18:30 ` Segher Boessenkool
2021-05-02 20:00 ` Joe Perches
2021-05-02 20:32 ` Segher Boessenkool
2021-05-02 21:05 ` Ali Kaasinen
2021-05-02 21:08 ` Linus Torvalds
2021-05-02 22:30 ` Matthew Wilcox
2021-05-03 7:34 ` Alexander Dahl
2021-05-03 8:54 ` Joe Perches
2021-05-03 9:25 ` Arnd Bergmann
2021-05-03 12:20 ` David Laight
2021-05-03 13:10 ` Miguel Ojeda
2021-05-04 5:30 ` Alexander Dahl
2021-05-04 6:33 ` Christophe Leroy
2021-05-04 12:07 ` Arnd Bergmann
2021-05-04 13:25 ` Andy Shevchenko
2021-05-03 11:35 ` Arnd Bergmann
2021-05-03 9:49 ` Kirill A. Shutemov
2021-05-02 21:23 ` Joe Perches
2021-05-03 0:44 ` Segher Boessenkool
2021-05-03 9:57 ` Arnd Bergmann
2021-05-04 7:56 ` Ben Dooks
2021-05-04 8:38 ` Miguel Ojeda [this message]
2021-05-04 9:22 ` Michal Suchánek
2021-05-04 12:09 ` Miguel Ojeda
2021-05-04 12:17 ` Michal Suchánek
2021-05-04 12:26 ` Christophe Leroy
2021-05-02 18:37 ` Segher Boessenkool
2021-05-03 6:16 ` Christophe Leroy
2021-05-04 2:13 ` Masahiro Yamada
2021-05-04 13:18 ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-15 7:14 ` Pavel Machek
2021-05-15 7:27 ` Joe Perches
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=CANiq72mk84uay--BWOLT4zF12-rat9erohKazB8SpTPoVCTX1A@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=ben.dooks@codethink.co.uk \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).