From: Jonathan Corbet <corbet@lwn.net>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] Documentation/printf: Use literal fwnode_handle
Date: Mon, 11 Aug 2025 11:00:44 -0600 [thread overview]
Message-ID: <87ldnpeqtf.fsf@trenco.lwn.net> (raw)
In-Reply-To: <07262c55e82fc4a3e3dbe7c45713b14955271e7f.1754552156.git.geert+renesas@glider.be>
Geert Uytterhoeven <geert+renesas@glider.be> writes:
> When looking for fwnode_handle in the printk format documentation, it is
> only found in the Chinese translation:
>
> $ git grep fwnode_handle -- Documentation/*printk-formats.rst
> Documentation/translations/zh_CN/core-api/printk-formats.rst:用于打印fwnode_handles的消息。默认情况下是打印完整的节点名称,包括路径。
>
> This happens because the original documentation talks about "fwnode
> handles", without mentioning the actual type name.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/core-api/printk-formats.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/printk-formats.rst b/Documentation/core-api/printk-formats.rst
> index 4b7f3646ec6ce028..7f2f11b482865175 100644
> --- a/Documentation/core-api/printk-formats.rst
> +++ b/Documentation/core-api/printk-formats.rst
> @@ -521,7 +521,7 @@ Fwnode handles
>
> %pfw[fP]
>
> -For printing information on fwnode handles. The default is to print the full
> +For printing information on an fwnode_handle. The default is to print the full
> node name, including the path. The modifiers are functionally equivalent to
Applied, thanks.
jon
prev parent reply other threads:[~2025-08-11 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:36 Geert Uytterhoeven
2025-08-09 9:57 ` Andy Shevchenko
2025-08-10 7:33 ` Geert Uytterhoeven
2025-08-11 6:08 ` Sakari Ailus
2025-08-11 8:28 ` Kunwu Chan
2025-08-11 17: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=87ldnpeqtf.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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®