From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-actions@lists.infradead.org
Cc: "Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: Re: [PATCH] Documentation: parport-lowlevel: Separate function listing code blocks
Date: Mon, 10 Nov 2025 12:48:18 -0700 [thread overview]
Message-ID: <87ecq5y8hp.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251105124947.45048-1-bagasdotme@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> Commit be9d0411f1608a ("parport-lowlevel.txt: standardize document
> format") reSTify parport interface documentation but forgets to properly
> mark function listing code blocks up. As such, these are rendered as
> long-running normal paragraph instead.
>
> Fix them by adding missing separator between the code block marker and
> the listing.
>
> Fixes: be9d0411f1608a ("parport-lowlevel.txt: standardize document format")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/driver-api/parport-lowlevel.rst | 5 +++++
> 1 file changed, 5 insertions(+)
Applied, thanks.
jon
prev parent reply other threads:[~2025-11-10 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 12:49 [PATCH] Documentation: parport-lowlevel: Separate function listing code blocks Bagas Sanjaya
2025-11-06 5:55 ` Randy Dunlap
2025-11-10 19:48 ` 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=87ecq5y8hp.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=afaerber@suse.de \
--cc=bagasdotme@gmail.com \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mchehab@kernel.org \
--cc=sudipm.mukherjee@gmail.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