From: Jonathan Corbet <corbet@lwn.net>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: <linux-doc@vger.kernel.org>, <paulmck@kernel.org>,
<tj@kernel.org>, <jiangshanlai@gmail.com>,
<wanghaibin.wang@huawei.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: kthread: Fix WQ_SYSFS workqueues path name
Date: Mon, 2 Mar 2020 13:05:17 -0700 [thread overview]
Message-ID: <20200302130517.075f97ee@lwn.net> (raw)
In-Reply-To: <20200225124052.1506-1-yuzenghui@huawei.com>
On Tue, 25 Feb 2020 20:40:52 +0800
Zenghui Yu <yuzenghui@huawei.com> wrote:
> The set of WQ_SYSFS workqueues should be displayed using
> "ls /sys/devices/virtual/workqueue", add the missing '/'.
>
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
> Documentation/admin-guide/kernel-per-CPU-kthreads.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/kernel-per-CPU-kthreads.rst b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst
> index baeeba8762ae..21818aca4708 100644
> --- a/Documentation/admin-guide/kernel-per-CPU-kthreads.rst
> +++ b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst
> @@ -234,7 +234,7 @@ To reduce its OS jitter, do any of the following:
> Such a workqueue can be confined to a given subset of the
> CPUs using the ``/sys/devices/virtual/workqueue/*/cpumask`` sysfs
> files. The set of WQ_SYSFS workqueues can be displayed using
> - "ls sys/devices/virtual/workqueue". That said, the workqueues
> + "ls /sys/devices/virtual/workqueue". That said, the workqueues
> maintainer would like to caution people against indiscriminately
> sprinkling WQ_SYSFS across all the workqueues. The reason for
> caution is that it is easy to add WQ_SYSFS, but because sysfs is
Applied, thanks.
jon
prev parent reply other threads:[~2020-03-02 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 12:40 [PATCH] Documentation: kthread: Fix WQ_SYSFS workqueues path name Zenghui Yu
2020-03-02 20:05 ` 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=20200302130517.075f97ee@lwn.net \
--to=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=tj@kernel.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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