mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Ariful Islam Shoikot <islamarifulshoikat@gmail.com>,
	linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: clarify wording in programming-language.rst
Date: Sat, 14 Feb 2026 09:55:32 -0800	[thread overview]
Message-ID: <156baf88-cd00-4bbc-917a-0b1b9b79b2cd@infradead.org> (raw)
In-Reply-To: <87ms1bqmh0.fsf@trenco.lwn.net>



On 2/14/26 9:11 AM, Jonathan Corbet wrote:
> Ariful Islam Shoikot <islamarifulshoikat@gmail.com> writes:
> 
>> Clarify that the Linux kernel is written in C and improve
>> punctuation in the clang sentence.
>>
>> Signed-off-by: Ariful Islam Shoikot <islamarifulshoikat@gmail.com>
>> ---
>>  Documentation/process/programming-language.rst | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/process/programming-language.rst b/Documentation/process/programming-language.rst
>> index f39d1d3dd9ce..c18e307ccb56 100644
>> --- a/Documentation/process/programming-language.rst
>> +++ b/Documentation/process/programming-language.rst
>> @@ -3,10 +3,10 @@
>>  Programming Language
>>  ====================
>>  
>> -The kernel is written in the C programming language [c-language]_.
>> -More precisely, the kernel is typically compiled with ``gcc`` [gcc]_
>> +The Linux kernel is written in the C programming language [c-language]_.
>> +More precisely, it is typically compiled with ``gcc`` [gcc]_
>>  under ``-std=gnu11`` [gcc-c-dialect-options]_: the GNU dialect of ISO C11.
>> -``clang`` [clang]_ is also supported, see docs on
>> +``clang`` [clang]_ is also supported; see documentation on
>>  :ref:`Building Linux with Clang/LLVM <kbuild_llvm>`.
> 
> So you have tidied up the language, but not addressed the fact that the
> information is somewhat outdated.  Clang is a first-class option these
> days, and the documentation should probably reflect that.
> 
> Oh well, I've applied this as a good start :)


Maybe mention Rust as well?
-- 
~Randy


      reply	other threads:[~2026-02-14 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14 13:28 Ariful Islam Shoikot
2026-02-14 17:11 ` Jonathan Corbet
2026-02-14 17:55   ` Randy Dunlap [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=156baf88-cd00-4bbc-917a-0b1b9b79b2cd@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=islamarifulshoikat@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®