From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/printf: Use literal fwnode_handle
Date: Mon, 11 Aug 2025 06:08:01 +0000 [thread overview]
Message-ID: <aJmIwb84CPvswmaQ@kekkonen.localdomain> (raw)
In-Reply-To: <CAMuHMdXF_Dto3EVBKxr9+M=rmcwNcZy66aUqbb5OiRb75vSfnA@mail.gmail.com>
Hi Geert,
On Sun, Aug 10, 2025 at 09:33:50AM +0200, Geert Uytterhoeven wrote:
> Hi Andy,
>
> CC Sakari
>
> On Sat, 9 Aug 2025 at 11:57, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Aug 07, 2025 at 09:36:01AM +0200, Geert Uytterhoeven wrote:
> > > 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.
> >
> > Fixes?
>
> If you insist...
>
> Fixes: 3bd32d6a2ee62db3 ("lib/vsprintf: Add %pfw conversion specifier
> for printing fwnode names")
Thanks for the patch.
Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2025-08-11 6:08 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 [this message]
2025-08-11 8:28 ` Kunwu Chan
2025-08-11 17:00 ` Jonathan Corbet
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=aJmIwb84CPvswmaQ@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--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®