mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Libin (Huawei)" <huawei.libin@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>
Cc: <mingo@redhat.com>, <linux-kernel@vger.kernel.org>,
	<guohanjun@huawei.com>
Subject: Re: [PATCH 0/2] sched: pick and check task if double_lock_balance() unlock the rq
Date: Thu, 12 Apr 2018 20:24:01 +0800	[thread overview]
Message-ID: <cf6c700d-080f-05f8-373b-62f543fa3cd7@huawei.com> (raw)
In-Reply-To: <20180412082010.3f088370@gandalf.local.home>



在 2018/4/12 20:20, Steven Rostedt 写道:
> On Thu, 12 Apr 2018 14:11:45 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
> 
>> On Thu, Apr 12, 2018 at 06:58:53PM +0800, Li Bin wrote:
>>> Li Bin (1):
>>>    sched/deadline.c: pick and check task if double_lock_balance() unlock
>>>      the rq
>>>
>>> Zhou Chengming (1):
>>>    sched/rt.c: pick and check task if double_lock_balance() unlock the
>>>      rq
>>>    
>>
>> Much thanks!
>>
>> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>>
>> Ingo, please apply.
> 
> You can add my:
> 
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> 
> but I would still like to see the declaration of next_task before the
> comment, just for style concerns.

Ok, I will resend the patchset v2.

Thanks,
Li Bin

> 
> -- Steve
> 
> .
> 

      reply	other threads:[~2018-04-12 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 10:58 Li Bin
2018-04-12 10:58 ` [PATCH 1/2] sched/rt.c: " Li Bin
2018-04-12 12:10   ` Steven Rostedt
2018-04-12 10:58 ` [PATCH 2/2] sched/deadline.c: " Li Bin
2018-04-12 12:12   ` Steven Rostedt
2018-04-12 12:11 ` [PATCH 0/2] sched: " Peter Zijlstra
2018-04-12 12:20   ` Steven Rostedt
2018-04-12 12:24     ` Libin (Huawei) [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=cf6c700d-080f-05f8-373b-62f543fa3cd7@huawei.com \
    --to=huawei.libin@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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
Powered by JetHome