From: Nick Desaulniers <ndesaulniers@google.com>
To: Joe Perches <joe@perches.com>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Arvind Sankar <nivedita@alum.mit.edu>,
Masahiro Yamada <masahiroy@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Sami Tolvanen <samitolvanen@google.com>,
Andy Lavr <andy.lavr@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
"# 3.4.x" <stable@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v5] lib/string.c: implement stpcpy
Date: Tue, 15 Sep 2020 16:05:08 -0700 [thread overview]
Message-ID: <CAKwvOdn6ohOi-KSSOkC8BirHgXRRkbCk3Z_ySEyPPMg31cDB-A@mail.gmail.com> (raw)
In-Reply-To: <5a9007605dec96c81ec85bc3dcc78faaa9ed06a0.camel@perches.com>
On Mon, Sep 14, 2020 at 9:28 PM Joe Perches <joe@perches.com> wrote:
>
> On Mon, 2020-09-14 at 21:22 -0700, Nathan Chancellor wrote:
> > It would be nice to get this into mainline sooner rather than later so
> > that it can start filtering into the stable trees. ToT LLVM builds have
> > been broken for a month now.
>
> People that build stable trees with new compilers
> unsupported at the time the of the base version
> release are just asking for trouble.
It is asymmetry that we have a minimum supported version of a
toolchain, but no maximum supported version of a toolchain for a given
branch. I think that's a good thing; imagine if you were stuck on an
old compiler for a stable branch. No thanks. I guess we just like to
live dangerously? :P
Also, GKH has voiced support for newer toolchains for older kernel
releases before. Related to this issue, in fact.
https://lore.kernel.org/lkml/20200818072531.GC9254@kroah.com/
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2020-09-15 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 16:09 [PATCH v4] lib/string.c: implement stpcpy Nick Desaulniers
2020-09-14 16:14 ` Nick Desaulniers
2020-09-14 16:16 ` [PATCH v5] " Nick Desaulniers
2020-09-15 4:22 ` Nathan Chancellor
2020-09-15 4:28 ` Joe Perches
2020-09-15 23:05 ` Nick Desaulniers [this message]
2020-09-15 18:13 ` Nick Desaulniers
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=CAKwvOdn6ohOi-KSSOkC8BirHgXRRkbCk3Z_ySEyPPMg31cDB-A@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=andy.lavr@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=nivedita@alum.mit.edu \
--cc=samitolvanen@google.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;
as well as URLs for NNTP newsgroup(s).