From: Randy Dunlap <rdunlap@infradead.org>
To: Thomas Huth <thuth@redhat.com>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <david@davidgow.net>,
linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Rae Moar <raemoar63@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
workflows@vger.kernel.org
Subject: Re: [PATCH] Documentation: kunit: Fix bad debugfs path
Date: Thu, 10 Sep 2026 14:06:40 -0700 [thread overview]
Message-ID: <da556d54-9f53-4780-bab4-bf6fca89c82d@infradead.org> (raw)
In-Reply-To: <20260910135919.435500-1-thuth@redhat.com>
On 9/10/26 6:59 AM, Thomas Huth wrote:
> The path of debugfs is /sys/kernel/debug/ and not /sys/kernel/debugfs/.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/dev-tools/kunit/run_manual.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kunit/run_manual.rst b/Documentation/dev-tools/kunit/run_manual.rst
> index 98e8d5b288085..59c3313a6d15c 100644
> --- a/Documentation/dev-tools/kunit/run_manual.rst
> +++ b/Documentation/dev-tools/kunit/run_manual.rst
> @@ -87,7 +87,7 @@ the ``/sys/kernel/debug/kunit/<test_suite>/run`` file:
>
> .. code-block :: bash
>
> - echo "any string" > /sys/kernel/debugfs/kunit/<test_suite>/run
> + echo "any string" > /sys/kernel/debug/kunit/<test_suite>/run
>
> As a result, the test suite runs and the results are printed to the kernel
> log.
--
~Randy
prev parent reply other threads:[~2026-09-10 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 13:59 Thomas Huth
2026-09-10 21:06 ` Randy Dunlap [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=da556d54-9f53-4780-bab4-bf6fca89c82d@infradead.org \
--to=rdunlap@infradead.org \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=david@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=raemoar63@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=thuth@redhat.com \
--cc=workflows@vger.kernel.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
all inboxes | Powered by JetHome®