mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Albin Babu Varghese <albinbabuvarghese20@gmail.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Albin Babu Varghese <albinbabuvarghese20@gmail.com>
Subject: Re: [PATCH v2] Documentation: conf.py: remove repeated word in comment
Date: Thu, 21 Aug 2025 11:45:59 -0600	[thread overview]
Message-ID: <87ms7s7elk.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250820194714.130513-2-albinbabuvarghese20@gmail.com>

Albin Babu Varghese <albinbabuvarghese20@gmail.com> writes:

> Remove a repeated "are" from a comment in conf.py
>
> [v2] Resent with full recipient list. No changes from v1.
>
> Thanks, Albin

For future reference, information about resends and such should go below
the "---" line so that the maintainer does not have to edit them out
when applying the patch.  I have taken care of that this time around.

> Signed-off-by: Albin Babu Varghese <albinbabuvarghese20@gmail.com>
> ---
>  Documentation/conf.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 700516238d3f..55299665753a 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -224,7 +224,7 @@ author = "The kernel development community"
>  # |version| and |release|, also used in various other places throughout the
>  # built documents.
>  #
> -# In a normal build, version and release are are set to KERNELVERSION and
> +# In a normal build, version and release are set to KERNELVERSION and
>  # KERNELRELEASE, respectively, from the Makefile via Sphinx command line

Applied, thanks.

jon

      reply	other threads:[~2025-08-21 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 19:47 Albin Babu Varghese
2025-08-21 17:45 ` 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=87ms7s7elk.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=albinbabuvarghese20@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®