From: Qais Yousef <qyousef@layalina.io>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Xuewen Yan <xuewen.yan94@gmail.com>, Wei Wang <wvw@google.com>,
Jonathan JMChen <Jonathan.JMChen@mediatek.com>,
Hank <han.lin@mediatek.com>, Paul Bone <pbone@mozilla.com>
Subject: Re: [PATCH v2] Documentation: sched: Add a new sched-util-clamp.rst
Date: Sat, 3 Dec 2022 13:40:06 +0000 [thread overview]
Message-ID: <20221203134006.lj6uicaeo55npoq4@airbuntu> (raw)
In-Reply-To: <87cz976pwn.fsf@meer.lwn.net>
On 11/28/22 08:48, Jonathan Corbet wrote:
> Qais Yousef <qyousef@layalina.io> writes:
>
> > 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 v2:
> >
> > * Address various style comments from Bagas
>
> Just a handful of nits - this looks like a good addition to our
> documentation, thanks.
Thanks a lot Jonathan! I've taken all your comments into account. Thanks for
having a look and hopefully it wasn't a bad read!
Cheers
--
Qais Yousef
next prev parent reply other threads:[~2022-12-03 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 14:26 [PATCH v2] Documentation: sched: Add a new sched-util-clamp.rst Qais Yousef
2022-11-28 15:48 ` Jonathan Corbet
2022-12-03 13:40 ` Qais Yousef [this message]
2022-11-29 3:16 ` Bagas Sanjaya
2022-12-03 13:40 ` Qais Yousef
2022-11-29 10:32 ` Lukasz Luba
2022-12-03 13:40 ` Qais Yousef
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=20221203134006.lj6uicaeo55npoq4@airbuntu \
--to=qyousef@layalina.io \
--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=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=pbone@mozilla.com \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).