From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Improve wording on requirements for a free Nitrokey
Date: Fri, 5 Dec 2025 16:33:15 +0100 [thread overview]
Message-ID: <j6mj6stlk4ojprdpfvoa35ghsfics5wou4nh3khymmb2aiqxbr@73jzs33sbyly> (raw)
In-Reply-To: <aTIP2Wqspl-jfm7M@archie.me>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hello,
On Fri, Dec 05, 2025 at 05:48:57AM +0700, Bagas Sanjaya wrote:
> On Wed, Dec 03, 2025 at 08:43:47AM +0100, Uwe Kleine-König wrote:
> > diff --git a/Documentation/process/maintainer-pgp-guide.rst b/Documentation/process/maintainer-pgp-guide.rst
> > index b6919bf606c3..2e4da3de25d4 100644
> > --- a/Documentation/process/maintainer-pgp-guide.rst
> > +++ b/Documentation/process/maintainer-pgp-guide.rst
> > @@ -405,8 +405,8 @@ geographical region, and open/proprietary hardware considerations.
> >
> > .. note::
> >
> > - If you are listed in MAINTAINERS or have an account at kernel.org,
> > - you `qualify for a free Nitrokey Start`_ courtesy of The Linux
> > + If you are listed in an `M:` entry in MAINTAINERS or have an account at
> i.e. being listed as a maintainer?
Yes, that seems to be the criteria. This was at least the explanation
when a coworker with an R: entry wasn't able to apply (and the error
message gives no hint about the problem then).
> > + kernel.org, you `qualify for a free Nitrokey Start`_ courtesy of The Linux
> > Foundation.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-05 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 7:43 Uwe Kleine-König
2025-12-04 20:42 ` Konstantin Ryabitsev
2025-12-04 22:48 ` Bagas Sanjaya
2025-12-05 15:33 ` Uwe Kleine-König [this message]
2025-12-05 23:25 ` Bagas Sanjaya
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=j6mj6stlk4ojprdpfvoa35ghsfics5wou4nh3khymmb2aiqxbr@73jzs33sbyly \
--to=u.kleine-koenig@baylibre.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@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