From: Jonathan Corbet <corbet@lwn.net>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Kees Cook <keescook@chromium.org>,
Nathan Chancellor <natechancellor@gmail.com>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Randy Dunlap <rdunlap@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>, Borislav Petkov <bp@suse.de>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Will Deacon <will@kernel.org>,
clang-built-linux@googlegroups.com, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: add minimum clang/llvm version
Date: Mon, 31 Aug 2020 16:30:48 -0600 [thread overview]
Message-ID: <20200831163048.0cbeca5d@lwn.net> (raw)
In-Reply-To: <20200826191555.3350406-1-ndesaulniers@google.com>
On Wed, 26 Aug 2020 12:15:55 -0700
Nick Desaulniers <ndesaulniers@google.com> wrote:
> Based on a vote at the LLVM BoF at Plumbers 2020, we decided to start
> small, supporting just one formal upstream release of LLVM for now.
>
> We can probably widen the support window of supported versions over
> time. Also, note that LLVM's release process is different than GCC's.
> GCC tends to have 1 major release per year while releasing minor updates
> to the past 3 major versions. LLVM tends to support one major release
> and one minor release every six months.
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
> Tested-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> Tested-by: Nathan Chancellor <natechancellor@gmail.com>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Applied, thanks.
jon
prev parent reply other threads:[~2020-08-31 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 19:15 [PATCH v2] Documentation: add minimum clang/llvm version Nick Desaulniers
2020-08-27 18:24 ` Masahiro Yamada
2020-08-28 10:53 ` Will Deacon
2020-08-31 22:30 ` Jonathan Corbet [this message]
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=20200831163048.0cbeca5d@lwn.net \
--to=corbet@lwn.net \
--cc=bp@suse.de \
--cc=clang-built-linux@googlegroups.com \
--cc=grandmaster@al2klimov.de \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.org \
--cc=tytso@mit.edu \
--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).