From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-pm@vger.kernel.org
Cc: patches@lists.linux.dev, "Randy Dunlap" <rdunlap@infradead.org>,
"kernel test robot" <lkp@intel.com>,
"Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: power: supply: fix inline strings
Date: Mon, 02 Nov 2026 08:53:02 -0700 [thread overview]
Message-ID: <87jymvdych.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261008171203.3080111-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Consistently use `string` to quote code symbols.
> This repairs the docs build warning:
>
> Documentation/power/power_supply_class.rst:211: WARNING: Inline emphasis start-string without end-string. [docutils]
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202610050416.L69x2Wpo-lkp@intel.com/
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>
> Cc: Sebastian Reichel <sebastian.reichel@collabora.com>
> Cc: linux-pm@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: linux-doc@vger.kernel.org
>
> Documentation/power/power_supply_class.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2026-11-02 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 17:12 [PATCH] docs: power: supply: fix inline strings Randy Dunlap
2026-11-02 15:53 ` 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=87jymvdych.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=ivanrwcm25@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=sebastian.reichel@collabora.com \
--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