From: Qais Yousef <qyousef@layalina.io>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org, 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] Documentation: sched: Add a new sched-util-clamp.rst
Date: Tue, 15 Nov 2022 20:55:59 +0000 [thread overview]
Message-ID: <20221115205559.5t2dkstfkytw2gpg@airbuntu> (raw)
In-Reply-To: <Y3GsX8XcDCHVa5UV@debian.me>
On 11/14/22 09:47, Bagas Sanjaya wrote:
> On Sat, Nov 05, 2022 at 11:23:43PM +0000, Qais Yousef wrote:
> > From: Qais Yousef <qais.yousef@arm.com>
> >
> > 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>
>
> Hmm, why didn't you send this patch from your arm address instead?
> On the other hand, thanks for including SoB from your sending address,
> which is different.
I changed jobs now; but started the patch when I was with Arm, hence the
2 SoBs.
>
> I will be commenting for the content on your fixup message.
Thanks for having a look!
Cheers
--
Qais Yousef
next prev parent reply other threads:[~2022-11-15 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 23:23 [PATCH] Documentation: sched: Add a new sched-util-clamp.rst Qais Yousef
2022-11-06 17:47 ` kernel test robot
2022-11-13 15:26 ` Qais Yousef
2022-11-14 8:55 ` Bagas Sanjaya
2022-11-15 20:55 ` Qais Yousef
2022-11-16 8:36 ` Bagas Sanjaya
2022-11-20 20:52 ` Qais Yousef
2022-11-14 2:47 ` Bagas Sanjaya
2022-11-15 20:55 ` Qais Yousef [this message]
2022-11-14 9:22 ` Bagas Sanjaya
2022-11-15 20:55 ` 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=20221115205559.5t2dkstfkytw2gpg@airbuntu \
--to=qyousef@layalina.io \
--cc=Jonathan.JMChen@mediatek.com \
--cc=bagasdotme@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=han.lin@mediatek.com \
--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 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.