From: Jonathan Corbet <corbet@lwn.net>
To: Benjamin Poirier <bpoirier@nvidia.com>
Cc: Thorsten Blum <thorsten.blum@toblux.com>,
Luis Chamberlain <mcgrof@kernel.org>,
David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Add detailed explanation for 'N' taint flag
Date: Mon, 29 Jul 2024 15:45:35 -0600 [thread overview]
Message-ID: <87jzh398jk.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240717203521.514348-1-bpoirier@nvidia.com>
Benjamin Poirier <bpoirier@nvidia.com> writes:
> Every taint flag has an entry in the "More detailed explanation" section
> except for the 'N' flag. That omission was probably just an oversight so
> add an entry for that flag.
>
> Fixes: 2852ca7fba9f ("panic: Taint kernel if tests are run")
> Signed-off-by: Benjamin Poirier <bpoirier@nvidia.com>
> ---
> Documentation/admin-guide/tainted-kernels.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
> index f92551539e8a..700aa72eecb1 100644
> --- a/Documentation/admin-guide/tainted-kernels.rst
> +++ b/Documentation/admin-guide/tainted-kernels.rst
> @@ -182,3 +182,5 @@ More detailed explanation for tainting
> produce extremely unusual kernel structure layouts (even performance
> pathological ones), which is important to know when debugging. Set at
> build time.
> +
> + 18) ``N`` if an in-kernel test, such as a KUnit test, has been run.
Applied, thanks.
jon
prev parent reply other threads:[~2024-07-29 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 20:35 Benjamin Poirier
2024-07-17 21:11 ` Luis Chamberlain
2024-07-18 5:55 ` David Gow
2024-07-29 21:45 ` 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=87jzh398jk.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bpoirier@nvidia.com \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=thorsten.blum@toblux.com \
/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®