From: Jonathan Corbet <corbet@lwn.net>
To: Nicolas Schier <nicolas@fjasle.eu>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Nicolas Schier <nicolas@fjasle.eu>
Subject: Re: [PATCH 0/2] Documentation: Add my name to the Kernel Statements
Date: Fri, 24 Jul 2026 07:34:44 -0600 [thread overview]
Message-ID: <87cxwc8qa3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260724-sign-kernel-statements-v1-0-52131fb5affb@fjasle.eu>
Nicolas Schier <nicolas@fjasle.eu> writes:
> Recently, I stumbled over the Kernel Driver Statement and the
> Linux Kernel License Enforcement Statement and wondered why I
> never before had seen them. They express strong convictions,
> which I do share and support, in clear words. I gladly sign
> both statements.
>
> Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
> ---
> Nicolas Schier (2):
> Documentation: Add my name to the Kernel Driver Statement
> Documentation: Add my name to the Kernel Enforcement Statement
>
> Documentation/process/kernel-driver-statement.rst | 1 +
> Documentation/process/kernel-enforcement-statement.rst | 1 +
> 2 files changed, 2 insertions(+)
These files have been static for the better part of a decade, and have
made their point. I'd really rather not start adding names to them
again now...
Thanks,
jon
prev parent reply other threads:[~2026-07-24 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 4:48 [PATCH 0/2] Documentation: Add my name to the Kernel Statements Nicolas Schier
2026-07-24 4:48 ` [PATCH 1/2] Documentation: Add my name to the Kernel Driver Statement Nicolas Schier
2026-07-24 4:48 ` [PATCH 2/2] Documentation: Add my name to the Kernel Enforcement Statement Nicolas Schier
2026-07-24 13:34 ` 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=87cxwc8qa3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas@fjasle.eu \
--cc=skhan@linuxfoundation.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