From: Quentin Perret <qperret@google.com>
To: Patrick Bellasi <patrick.bellasi@matbug.net>
Cc: Doug Anderson <dianders@chromium.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
juri.lelli@redhat.com,
Vincent Guittot <vincent.guittot@linaro.org>,
dietmar.eggemann@arm.com, Steven Rostedt <rostedt@goodmis.org>,
Benjamin Segall <bsegall@google.com>,
mgorman@suse.de, ctheegal@codeaurora.org,
valentin.schneider@arm.com, qais.yousef@arm.com,
LKML <linux-kernel@vger.kernel.org>,
kernel-team@android.com
Subject: Re: [PATCH] sched/core: Fix reset-on-fork from RT with uclamp
Date: Thu, 16 Apr 2020 09:54:05 +0100 [thread overview]
Message-ID: <20200416085405.GA215493@google.com> (raw)
In-Reply-To: <20200415174718.GA30565@darkstar>
On Wednesday 15 Apr 2020 at 19:47:18 (+0200), Patrick Bellasi wrote:
> Honestly I was almost there to ask for the same cleanup. :)
>
> If you get rid of the useless variable we can go back to the exact
> same code modified by the commit we are fixing, i.e. 1a00d999971c.
>
> So, not strong opinions here too, but if it's not a big problem I
> would post a cleaned up v2.
Alright, that works for me. I'll send a v2 shortly.
Thanks!
Quentin
prev parent reply other threads:[~2020-04-16 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 16:13 [PATCH] sched/core: Fix reset-on-fork from RT with uclamp Quentin Perret
2020-04-14 16:21 ` Joel Fernandes
2020-04-14 16:27 ` Quentin Perret
2020-04-14 16:32 ` Joel Fernandes
2020-04-14 17:21 ` Patrick Bellasi
2020-04-14 17:25 ` Quentin Perret
2020-04-14 20:45 ` Doug Anderson
2020-04-15 8:20 ` Quentin Perret
2020-04-15 16:31 ` Doug Anderson
2020-04-15 17:47 ` Patrick Bellasi
2020-04-16 8:54 ` Quentin Perret [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=20200416085405.GA215493@google.com \
--to=qperret@google.com \
--cc=bsegall@google.com \
--cc=ctheegal@codeaurora.org \
--cc=dianders@chromium.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@matbug.net \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rostedt@goodmis.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox