From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v3 2/2] sched/core: Get rid of 'cpu' local variable in __schedule()
Date: Wed, 2 Mar 2016 13:05:01 +0100 [thread overview]
Message-ID: <20160302120501.GE6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <087fca802283fabd6697f99be0a027c26c0c506b.1456919394.git.agordeev@redhat.com>
On Wed, Mar 02, 2016 at 12:53:32PM +0100, Alexander Gordeev wrote:
> This update is a continuation of commit 3223d05 ("sched/core:
Please put
[core]
abbrev = 12
Into your .gitconfig, 7 char SHA1s are no good.
If TJ acks the first, I can fix up this time, so no need to repost just
yet.
prev parent reply other threads:[~2016-03-02 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 11:53 [PATCH v3 0/2] sched/core: Cleanup leftovers in __schedule() Alexander Gordeev
2016-03-02 11:53 ` [PATCH v3 1/2] sched/core: Get rid of 'cpu' argument in wq_worker_sleeping() Alexander Gordeev
2016-03-02 12:03 ` Peter Zijlstra
2016-03-02 15:28 ` Tejun Heo
2016-03-02 11:53 ` [PATCH v3 2/2] sched/core: Get rid of 'cpu' local variable in __schedule() Alexander Gordeev
2016-03-02 12:05 ` Peter Zijlstra [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=20160302120501.GE6356@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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.