All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bartlomiej Kubik <kubik.bartlomiej@gmail.com>
Cc: skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	rdunlap@infradead.org,
	Bartlomiej Kubik <kubik.bartlomiej@gmail.com>
Subject: Re: [PATCH v3] docs: replace a duplicated word and add missing SPDX-License tag
Date: Thu, 21 Aug 2025 11:58:26 -0600	[thread overview]
Message-ID: <87ect47e0t.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250819113551.34356-1-kubik.bartlomiej@gmail.com>

Bartlomiej Kubik <kubik.bartlomiej@gmail.com> writes:

> Fix documentation issues by removing a duplicated word and adding the
> missing SPDX-License identifier.
>
> Signed-off-by: Bartlomiej Kubik <kubik.bartlomiej@gmail.com>
> ---
>
> Changelog:
>
> Changes since v2:
> - Replace “that” with “the.”
>
> Changes since v1:		
> - Add missing SPDX-License tag
> - Remove duplicated word "that"
>
>  Documentation/admin-guide/kernel-parameters.rst | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

A couple of minor notes:

- It is good to indicate *which* file you are modifying; I've rewritten
  the subject line to that end.

- Adding SPDX headers is a bit fraught unless you are truly sure of the
  license under which the file was contributed.  Given the nature of
  this file and all of the people who have touched it, though, GPLv2 is
  the only option that makes any sense.

Applied, thanks.

jon

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 11:35 [PATCH v3] docs: replace a duplicated word and add missing SPDX-License tag Bartlomiej Kubik
2025-08-19 17:19 ` Randy Dunlap
2025-08-21 17:58 ` Jonathan Corbet [this message]
2025-08-22  9:28   ` Bartłomiej Kubik

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=87ect47e0t.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=kubik.bartlomiej@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.