From: Randy Dunlap <rdunlap@infradead.org>
To: Costa Shulyupin <costa.shul@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] docs: kernel-parameters: Fix stale sticore file paths
Date: Sun, 31 May 2026 09:09:08 -0700 [thread overview]
Message-ID: <9ba41c93-ff40-4a82-9c2e-d86a892f83d9@infradead.org> (raw)
In-Reply-To: <20260531140541.4115641-1-costa.shul@redhat.com>
On 5/31/26 7:05 AM, Costa Shulyupin wrote:
> Update file paths for sticore references that
> became stale when drivers were reorganized:
> - drivers/video/console/sticore.c -> drivers/video/
>
> Assisted-by: Claude:claude-opus-4-6
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/admin-guide/kernel-parameters.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 459ed0d72aeb..f94ec9f3a75c 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -7381,10 +7381,10 @@ Kernel parameters
> Set the STI (builtin display/keyboard on the HP-PARISC
> machines) console (graphic card) which should be used
> as the initial boot-console.
> - See also comment in drivers/video/console/sticore.c.
> + See also comment in drivers/video/sticore.c.
>
> sti_font= [HW]
> - See comment in drivers/video/console/sticore.c.
> + See comment in drivers/video/sticore.c.
>
> stifb= [HW]
> Format: bpp:<bpp1>[:<bpp2>[:<bpp3>...]]
--
~Randy
next prev parent reply other threads:[~2026-05-31 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 14:05 [PATCH v1] docs: kernel-parameters: Fix stale sticore file paths Costa Shulyupin
2026-05-31 16:09 ` Randy Dunlap [this message]
2026-06-01 19:08 ` 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=9ba41c93-ff40-4a82-9c2e-d86a892f83d9@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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