From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Costa Shulyupin <costa.shul@redhat.com>
Subject: Re: [PATCH v1] docs: sonypi: Fix stale header file path
Date: Mon, 01 Jun 2026 13:03:23 -0600 [thread overview]
Message-ID: <87tsrm84n8.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260531135850.4113774-1-costa.shul@redhat.com>
Costa Shulyupin <costa.shul@redhat.com> writes:
> The sonypi.h header was moved from drivers/char/ to
> include/linux/. Update the reference.
>
> Assisted-by: Claude:claude-opus-4-6
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> ---
> Documentation/admin-guide/laptops/sonypi.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/laptops/sonypi.rst b/Documentation/admin-guide/laptops/sonypi.rst
> index 7541f56e0007..fb8f4a30ddce 100644
> --- a/Documentation/admin-guide/laptops/sonypi.rst
> +++ b/Documentation/admin-guide/laptops/sonypi.rst
> @@ -89,7 +89,7 @@ statically linked into the kernel). Those options are:
> set to 0xffffffff, meaning that all possible events
> will be tried. You can use the following bits to
> construct your own event mask (from
> - drivers/char/sonypi.h)::
> + include/linux/sonypi.h)::
>
I suspect this driver has not been used in a long time, but as long as
it's around the documentation should at least not be obviously wrong.
Applied, thanks.
jon
prev parent reply other threads:[~2026-06-01 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 13:58 [PATCH v1] docs: sonypi: Fix stale header file path Costa Shulyupin
2026-06-01 19:03 ` 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=87tsrm84n8.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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