From: Randy Dunlap <rdunlap@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] docs: programming-languages: refresh blurb on clang support
Date: Tue, 29 Sep 2020 16:10:27 -0700 [thread overview]
Message-ID: <1925c4b7-2764-2b25-6aa4-a5001c8056f8@infradead.org> (raw)
In-Reply-To: <20200929211936.580805-1-ndesaulniers@google.com>
On 9/29/20 2:19 PM, Nick Desaulniers wrote:
> Building the kernel with Clang doesn't rely on third party patches, and
> has not for a few years now.
>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> ---
> Documentation/process/programming-language.rst | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/process/programming-language.rst b/Documentation/process/programming-language.rst
> index e5f5f065dc24..63af142d64ec 100644
> --- a/Documentation/process/programming-language.rst
> +++ b/Documentation/process/programming-language.rst
> @@ -6,14 +6,15 @@ Programming Language
> The kernel is written in the C programming language [c-language]_.
> More precisely, the kernel is typically compiled with ``gcc`` [gcc]_
> under ``-std=gnu89`` [gcc-c-dialect-options]_: the GNU dialect of ISO C90
> -(including some C99 features).
> +(including some C99 features). ``clang`` [clang]_ is also supported, see docs
Drop duplicated "docs" before here or after here.
checkpatch should have caught that.
> +docs on :ref:`Building Linux with Clang/LLVM <kbuild_llvm>`.
>
> This dialect contains many extensions to the language [gnu-extensions]_,
> and many of them are used within the kernel as a matter of course.
>
> -There is some support for compiling the kernel with ``clang`` [clang]_
> -and ``icc`` [icc]_ for several of the architectures, although at the time
> -of writing it is not completed, requiring third-party patches.
> +There is some support for compiling the kernel with ``icc`` [icc]_ for several
> +of the architectures, although at the time of writing it is not completed,
> +requiring third-party patches.
>
> Attributes
> ----------
>
thanks.
--
~Randy
next prev parent reply other threads:[~2020-09-29 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 21:19 [PATCH] docs: programming-languages: refresh blurb on clang support Nick Desaulniers
2020-09-29 23:10 ` Randy Dunlap [this message]
2020-09-30 16:21 ` Nathan Chancellor
2020-10-05 15:45 ` Jonathan Corbet
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=1925c4b7-2764-2b25-6aa4-a5001c8056f8@infradead.org \
--to=rdunlap@infradead.org \
--cc=clang-built-linux@googlegroups.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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).