From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Kees Cook <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: sphinx: add missing SPDX tags
Date: Wed, 25 Jun 2025 12:41:01 -0600 [thread overview]
Message-ID: <871pr7acle.fsf@trenco.lwn.net> (raw)
In-Reply-To: <1a62226c5fe524eb87bdb80b33bc7ec880a68880.1750585188.git.mchehab+huawei@kernel.org>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Several Sphinx extensions and tools are missing SPDX tags.
> Add them.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/sphinx/cdomain.py | 1 +
> Documentation/sphinx/kernel_include.py | 1 +
> Documentation/sphinx/kerneldoc.py | 1 +
> Documentation/sphinx/kfigure.py | 1 +
> Documentation/sphinx/load_config.py | 1 +
> Documentation/sphinx/min_requirements.txt | 1 +
> Documentation/sphinx/parse-headers.pl | 5 ++++-
> Documentation/sphinx/requirements.txt | 1 +
> Documentation/sphinx/rstFlatTable.py | 1 +
> 9 files changed, 12 insertions(+), 1 deletion(-)
I've applied this, but the patch led me to wonder...
> diff --git a/Documentation/sphinx/cdomain.py b/Documentation/sphinx/cdomain.py
> index e8ea80d4324c..3dc285dc70f5 100644
> --- a/Documentation/sphinx/cdomain.py
> +++ b/Documentation/sphinx/cdomain.py
> @@ -1,4 +1,5 @@
> # -*- coding: utf-8; mode: python -*-
Do we really need these lines? UTF8 should be the default almost
anywhere, and Emacs understands that a .py file will require Python
mode...
Thanks,
jon
next prev parent reply other threads:[~2025-06-25 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 9:39 [PATCH] docs: sphinx: add missing SPDX tags Mauro Carvalho Chehab
2025-06-25 18:41 ` Jonathan Corbet [this message]
2025-06-25 20:11 ` Mauro Carvalho Chehab
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=871pr7acle.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.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