workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amitabh <amitabh@amidevlab.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs: process: maintainer-pgp-guide: update kernel.org docs link
Date: Thu, 5 Feb 2026 20:45:52 +0530	[thread overview]
Message-ID: <E285CDA1-776F-44AF-9C6D-AB43F4EC5054@amidevlab.com> (raw)
In-Reply-To: <875x8bi6su.fsf@trenco.lwn.net>

Hi Jon,

> On 5 Feb 2026, at 8:19 PM, Jonathan Corbet <corbet@lwn.net> wrote:
> 
> Amitabh Srivastava <amitabh@amidevlab.com> writes:
> 
>> Update http link to the documentation about how to add a kernel.org UID to
>> the maintainer's key. Add missing SPDX-License-Identifier to fix a
>> checkpatch warning.
>> 
>> Signed-off-by: Amitabh Srivastava <amitabh@amidevlab.com>
>> ---
>> Documentation/process/maintainer-pgp-guide.rst | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>> 
>> diff --git a/Documentation/process/maintainer-pgp-guide.rst b/Documentation/process/maintainer-pgp-guide.rst
>> index b6919bf606c3..1e4d885dc784 100644
>> --- a/Documentation/process/maintainer-pgp-guide.rst
>> +++ b/Documentation/process/maintainer-pgp-guide.rst
>> @@ -1,3 +1,5 @@
>> +.. SPDX-License-Identifier: GPL-2.0
>> +
> 
> Do you know that was the intended license for this file?  We need to be
> careful about putting license declarations on other people's work.
> 
Yes, The Linux kernel documentation is typically licensed under GPL-2.0.
Other files in the directory contain the same 'SPDX-License-Identifier' as well.
However, I have added this just to satisfy checkpatch.pl requirement, which
checks for missing license information in documentation files. Let me know if
you think otherwise.

> Thanks,
> 
> jon


  reply	other threads:[~2026-02-05 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 11:55 Amitabh Srivastava
2026-02-05 13:23 ` Geert Uytterhoeven
2026-02-05 14:14   ` Amitabh
2026-02-05 14:49 ` Jonathan Corbet
2026-02-05 15:15   ` Amitabh [this message]
2026-02-05 15:30     ` Jonathan Corbet
     [not found]       ` <3AB51D59-A054-4847-91CD-DFF3A2EB5F04@amidevlab.com>
2026-02-06 14:20         ` Konstantin Ryabitsev
2026-02-06 14:38 ` Konstantin Ryabitsev
2026-02-06 16:04   ` Jonathan Corbet
2026-02-06 20:43     ` Amitabh
2026-02-09 19:51 ` Jonathan Corbet

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=E285CDA1-776F-44AF-9C6D-AB43F4EC5054@amidevlab.com \
    --to=amitabh@amidevlab.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=workflows@vger.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