From: Amitabh <amitabh@amidevlab.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
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: Fri, 6 Feb 2026 20:02:50 +0530 [thread overview]
Message-ID: <95CDB1C3-56CE-4A7A-92F4-AD717BA4C956@amidevlab.com> (raw)
In-Reply-To: <20260206-fluorescent-straight-partridge-cf42ef@lemur>
Thank you, Konstantin.
Hope you won’t mind giving a "Reviewed-by" to my patch :)
> On 6 Feb 2026, at 7:50 PM, Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>
> On Fri, Feb 06, 2026 at 12:02:00AM +0530, Amitabh wrote:
>>> I am aware of kernel documentation practices :) "Typically licensed"
>>> does not tell you what any individual contributor intended, though.
>>> *Probably* that tag is OK, but you should really consult with the
>>> original author of that page to ask what their intent was.
>>
>> You are absolutely correct. In fact, the original author, Konstantin Ryabitsev,
>> (in TO here) responded to my v1 patch in the affirmative regarding the changes.
>> (https://lore.kernel.org/all/177006480695.901069.1641199463436529014@lemur/)
>
> Yes, that matches the intended license.
>
> -K
Regards
Amitabh
next prev parent reply other threads:[~2026-02-06 14:40 UTC|newest]
Thread overview: 12+ 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
[not found] ` <E285CDA1-776F-44AF-9C6D-AB43F4EC5054@amidevlab.com>
2026-02-05 15:30 ` Jonathan Corbet
2026-02-05 18:32 ` Amitabh
2026-02-06 14:20 ` Konstantin Ryabitsev
2026-02-06 14:32 ` Amitabh [this message]
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=95CDB1C3-56CE-4A7A-92F4-AD717BA4C956@amidevlab.com \
--to=amitabh@amidevlab.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®