From: Jonathan Corbet <corbet@lwn.net>
To: "Yahya Toubali" <yahya@yahyatoubali.me>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"open list:CONTROL GROUP (CGROUP)" <cgroups@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
"open list:SOUND" <linux-sound@vger.kernel.org>
Cc: Yahya Toubali <yahya@yahyatoubali.me>
Subject: Re: [PATCH v3] Documentation: add SPDX license identifiers to RST files
Date: Wed, 22 Jul 2026 10:29:58 -0600 [thread overview]
Message-ID: <87y0f3asxl.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260718165618.1923627-1-yahya@yahyatoubali.me>
Yahya Toubali <yahya@yahyatoubali.me> writes:
> Add SPDX-License-Identifier: GPL-2.0 to RST documentation files
> that were missing it. This aligns with kernel documentation
> conventions.
>
> Signed-off-by: Yahya Toubali <yahya@yahyatoubali.me>
> ---
> Documentation/admin-guide/cgroup-v2.rst | 1 +
> Documentation/core-api/housekeeping.rst | 2 ++
> Documentation/core-api/memory-allocation.rst | 1 +
> Documentation/doc-guide/sphinx.rst | 1 +
> Documentation/process/5.Posting.rst | 1 +
> Documentation/process/howto.rst | 1 +
> Documentation/sound/designs/index.rst | 2 ++
> 7 files changed, 9 insertions(+)
In addition to Greg's comments, you'll want to split these out, since
they need to be judged by different maintainers.
Also, have you verified that GPL-2.0 is the intended license for all of
those files? I wrote one of them and big parts of another, but you
haven't asked me...
Thanks,
jon
prev parent reply other threads:[~2026-07-22 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 16:56 [PATCH v3] Documentation: add SPDX license identifiers to RST files Yahya Toubali
2026-07-19 5:26 ` Greg KH
2026-07-22 16:29 ` 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=87y0f3asxl.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=perex@perex.cz \
--cc=skhan@linuxfoundation.org \
--cc=tiwai@suse.com \
--cc=tj@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=yahya@yahyatoubali.me \
/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