linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev
Subject: Re: [PATCH] Documentation: kernel-hacking: minor edits for style
Date: Tue, 05 Apr 2022 09:54:57 -0600	[thread overview]
Message-ID: <87v8vned9q.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220329195117.azs4kaflc6ksfzdh@meerkat.local>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> Rusty's kernel-hacking guides provide important information, however
> they are written in a narrative style that some readers may interpret as
> off-putting. Since the goal is to make kernel documentation accessible
> to as many new developers as possible, it's best to avoid the turns of
> phrase that require a specific cultural context to properly understand.
>
> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> ---
>  Documentation/kernel-hacking/hacking.rst | 36 ++++++++++++------------
>  Documentation/kernel-hacking/locking.rst |  5 +---
>  2 files changed, 19 insertions(+), 22 deletions(-)

*Sigh*...it's kind of sad to see the character of Rusty's writing being
chipped away over time; this isn't the first sanitization patch applied
to this file.  It certainly needs a lot more work than this to match
current practice.  Oh well, I've applied it, thanks.

jon

      parent reply	other threads:[~2022-04-05 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 19:51 [PATCH] Documentation: kernel-hacking: minor edits for style Konstantin Ryabitsev
2022-03-30  0:50 ` Daniel Axtens
2022-04-05 15:54 ` 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=87v8vned9q.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    /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).