linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Lublin <daniel@lublin.se>
Cc: Daniel Lublin <daniel@lublin.se>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: add reference from dynamic debug to loglevel kernel params
Date: Tue, 09 Jul 2024 09:00:14 -0600	[thread overview]
Message-ID: <87plrm8vb5.fsf@trenco.lwn.net> (raw)
In-Reply-To: <4633bdb82c1c7c014d79840887878624a55c59f8.1720533043.git.daniel@lublin.se>

Daniel Lublin <daniel@lublin.se> writes:

> This is useful information for somebody who has managed to dig into
> enabling debug output, but is wondering why there is no such output
> appearing on the console.
>
> Signed-off-by: Daniel Lublin <daniel@lublin.se>
> ---
>  Documentation/admin-guide/dynamic-debug-howto.rst | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/admin-guide/dynamic-debug-howto.rst b/Documentation/admin-guide/dynamic-debug-howto.rst
> index 0e9b48daf690..7c036590cd07 100644
> --- a/Documentation/admin-guide/dynamic-debug-howto.rst
> +++ b/Documentation/admin-guide/dynamic-debug-howto.rst
> @@ -26,6 +26,11 @@ Dynamic debug provides:
>     - format string
>     - class name (as known/declared by each module)
>  
> +NOTE: To actually get the debug-print output on the console, you may
> +need to adjust the kernel ``loglevel=``, or use ``ignore_loglevel``.
> +Read about these kernel parameters in
> +Documentation/admin-guide/kernel-parameters.rst.
> +

I've applied this, thanks.

jon

      reply	other threads:[~2024-07-09 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 13:51 [PATCH v2] Documentation: add reference from dynamic debug to loglevel kernel params Daniel Lublin
2024-07-09 15:00 ` 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=87plrm8vb5.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=daniel@lublin.se \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).