From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Kir Kolyshkin <kolyshkin@gmail.com>, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 04/10] docs: sched-bwc.rst: fix a typo on a doc name
Date: Wed, 19 May 2021 10:51:41 +0200 [thread overview]
Message-ID: <1dc0203bd7df375ef45832f0c88566e22c4138ff.1621413933.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1621413933.git.mchehab+huawei@kernel.org>
cgroupv2.rst -> cgroup-v2.rst
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/scheduler/sched-bwc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst
index 845eee659199..1fc73555f5c4 100644
--- a/Documentation/scheduler/sched-bwc.rst
+++ b/Documentation/scheduler/sched-bwc.rst
@@ -29,7 +29,7 @@ Quota and period are managed within the cpu subsystem via cgroupfs.
.. note::
The cgroupfs files described in this section are only applicable
to cgroup v1. For cgroup v2, see
- :ref:`Documentation/admin-guide/cgroupv2.rst <cgroup-v2-cpu>`.
+ :ref:`Documentation/admin-guide/cgroup-v2.rst <cgroup-v2-cpu>`.
- cpu.cfs_quota_us: the total available run-time within a period (in
microseconds)
--
2.31.1
next prev parent reply other threads:[~2021-05-19 8:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 8:51 [PATCH 00/10] Documentation build warning fixes Mauro Carvalho Chehab
2021-05-19 8:51 ` Mauro Carvalho Chehab
2021-05-19 8:51 ` Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 01/10] docs: update sysfs-platform_profile.rst reference Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 02/10] docs: vcpu-requests.rst: fix reference for atomic ops Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 03/10] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst Mauro Carvalho Chehab
2021-05-19 8:51 ` Mauro Carvalho Chehab [this message]
2021-05-19 8:51 ` [PATCH 05/10] docs: update pin-control.rst references Mauro Carvalho Chehab
2021-05-19 8:51 ` Mauro Carvalho Chehab
2021-05-19 10:20 ` Charles Keepax
2021-05-19 10:20 ` Charles Keepax
2021-05-19 14:43 ` Lee Jones
2021-05-19 14:43 ` Lee Jones
2021-05-25 0:30 ` Linus Walleij
2021-05-25 0:30 ` Linus Walleij
2021-05-19 8:51 ` [PATCH 06/10] docs: virt: api.rst: fix a pointer to SGX documentation Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 07/10] docs: ABI: iommu: remove duplicated definition for sysfs-kernel-iommu_groups Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 08/10] docs: ABI: sysfs-class-backlight: unify ambient light zone nodes Mauro Carvalho Chehab
2021-05-19 8:51 ` Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 09/10] docs: ABI: sysfs-class-led-trigger-pattern: remove repeat duplication Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 10/10] iio: documentation: fix a typo Mauro Carvalho Chehab
2021-05-20 20:08 ` Matthew Wilcox
2021-05-20 20:00 ` [PATCH 00/10] Documentation build warning fixes Jonathan Corbet
2021-05-20 20:00 ` Jonathan Corbet
2021-05-20 20:00 ` 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=1dc0203bd7df375ef45832f0c88566e22c4138ff.1621413933.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=kolyshkin@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.