From: Juri Lelli <juri.lelli@gmail.com>
To: Peng Hao <peng.hao2@zte.com.cn>
Cc: mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
andrea.parri@amarulasolutions.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/dl : return accurate release rq lock info
Date: Mon, 8 Oct 2018 10:47:53 +0200 [thread overview]
Message-ID: <20181008084753.GC9130@localhost.localdomain> (raw)
In-Reply-To: <1538788117-45448-1-git-send-email-peng.hao2@zte.com.cn>
On 06/10/18 09:08, Peng Hao wrote:
> find_lock_later_rq may or not releease rq lock when return
> later_rq=NULL, but it is fuzzy.
> If not releasing rq lock, it is unnecessary to re-call
> pick_next_pushable_dl_task.
>
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
Subject has whitespaces problems and changelog might be improved.
Other then that patch looks good, thanks!
Acked-by: Juri Lelli <juri.lelli@redhat.com>
prev parent reply other threads:[~2018-10-08 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 1:08 [PATCH] sched/dl : return accurate release rq lock info Peng Hao
2018-10-05 17:50 ` Steven Rostedt
2018-10-08 8:47 ` Juri Lelli [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=20181008084753.GC9130@localhost.localdomain \
--to=juri.lelli@gmail.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peng.hao2@zte.com.cn \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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