From: Lukasz Luba <lukasz.luba@arm.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Peter Zijlstra <peterz@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Xuewen Yan <xuewen.yan94@gmail.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@kernel.org>, Wei Wang <wvw@google.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Jonathan JMChen <Jonathan.JMChen@mediatek.com>,
Hank <han.lin@mediatek.com>, Paul Bone <pbone@mozilla.com>
Subject: Re: [PATCH v3] Documentation: sched: Document util clamp feature
Date: Wed, 21 Dec 2022 13:29:06 +0000 [thread overview]
Message-ID: <38c75f44-02ef-4501-ad68-2b9896c3b6b0@arm.com> (raw)
In-Reply-To: <20221216235716.201923-1-qyousef@layalina.io>
Hi Qais,
On 12/16/22 23:57, Qais Yousef wrote:
> The new util clamp feature needs a document explaining what it is and
> how to use it. The new document hopefully covers everything one needs to
> know about uclamp.
>
> Signed-off-by: Qais Yousef <qais.yousef@arm.com>
> Signed-off-by: Qais Yousef (Google) <qyousef@layalina.io>
> ---
>
> Changes in v3:
>
> * Addressed various readability and style comments from Bagas, Jonathan and
> Lukasz. Thanks all!
>
> Documentation/admin-guide/cgroup-v2.rst | 3 +
> Documentation/scheduler/index.rst | 1 +
> Documentation/scheduler/sched-util-clamp.rst | 741 +++++++++++++++++++
> 3 files changed, 745 insertions(+)
LGTM
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Regards,
Lukasz
prev parent reply other threads:[~2022-12-21 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 23:57 [PATCH v3] Documentation: sched: Document util clamp feature Qais Yousef
2022-12-17 9:53 ` Bagas Sanjaya
2022-12-17 22:01 ` Qais Yousef
2022-12-19 9:09 ` Lukasz Luba
2022-12-21 13:29 ` Lukasz Luba [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=38c75f44-02ef-4501-ad68-2b9896c3b6b0@arm.com \
--to=lukasz.luba@arm.com \
--cc=Jonathan.JMChen@mediatek.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=han.lin@mediatek.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbone@mozilla.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=vincent.guittot@linaro.org \
--cc=wvw@google.com \
--cc=xuewen.yan94@gmail.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