From: Jonathan Corbet <corbet@lwn.net>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>, ogabbay@kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jeffrey Hugo <quic_jhugo@quicinc.com>
Subject: Re: [PATCH] docs: accel: Fix debugfs path
Date: Tue, 24 Jan 2023 15:20:42 -0700 [thread overview]
Message-ID: <87mt67fubp.fsf@meer.lwn.net> (raw)
In-Reply-To: <1674145568-31513-1-git-send-email-quic_jhugo@quicinc.com>
Jeffrey Hugo <quic_jhugo@quicinc.com> writes:
> The device specific directory in debugfs does not have "accel". For
> example, the documentation says device 0 should have a debugfs entry as
> /sys/kernel/debug/accel/accel0/ but in reality the entry is
> /sys/kernel/debug/accel/0/
>
> Fix the documentation to match the implementation.
>
> Fixes: 8c5577a5ccc6 ("doc: add documentation for accel subsystem")
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> ---
> Documentation/accel/introduction.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/accel/introduction.rst b/Documentation/accel/introduction.rst
> index 6f31af1..11cade5 100644
> --- a/Documentation/accel/introduction.rst
> +++ b/Documentation/accel/introduction.rst
> @@ -69,7 +69,7 @@ The accelerator devices will be exposed to the user space with the dedicated
>
> - device char files - /dev/accel/accel*
> - sysfs - /sys/class/accel/accel*/
> -- debugfs - /sys/kernel/debug/accel/accel*/
> +- debugfs - /sys/kernel/debug/accel/*/
>
Applied, thanks.
jon
prev parent reply other threads:[~2023-01-24 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:26 [PATCH] docs: accel: Fix debugfs path Jeffrey Hugo
2023-01-19 16:28 ` Oded Gabbay
2023-01-24 22:20 ` 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=87mt67fubp.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.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;
as well as URLs for NNTP newsgroup(s).