From: Jonathan Corbet <corbet@lwn.net>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-parport@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: parport: Fix FIFO Kconfig symbol
Date: Mon, 31 Aug 2026 15:31:45 -0600 [thread overview]
Message-ID: <87ecfegeny.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260822082248.89651-1-kmehltretter@gmail.com>
Karl Mehltretter <kmehltretter@gmail.com> writes:
> The ReST conversion shortened CONFIG_PARPORT_PC_FIFO to the nonexistent
> CONFIG_FIFO symbol. Restore the full name.
>
> Fixes: e095f0711b49 ("Documentation/parport.txt: convert to ReST markup")
> Assisted-by: Codex:gpt-5.6-sol
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
> Documentation/admin-guide/parport.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/parport.rst b/Documentation/admin-guide/parport.rst
> index ad3f9b8a11e19..4aef45262bd49 100644
> --- a/Documentation/admin-guide/parport.rst
> +++ b/Documentation/admin-guide/parport.rst
> @@ -273,7 +273,7 @@ If that works fine, try with ``io=0x378 irq=7`` (adjust for your
> hardware), to make it use interrupt-driven in-software protocol.
>
> If **that** works fine, then one of the hardware modes isn't working
> -right. Enable ``CONFIG_FIFO`` (no, it isn't a module option,
> +right. Enable ``CONFIG_PARPORT_PC_FIFO`` (no, it isn't a module option,
> and yes, it should be), set the port to ECP mode in the BIOS and note
Applied, thanks.
jon
prev parent reply other threads:[~2026-08-31 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 8:22 [PATCH] docs: parport: Fix FIFO Kconfig symbol Karl Mehltretter
2026-08-22 17:03 ` Randy Dunlap
2026-08-31 21:31 ` 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=87ecfegeny.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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