From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: mingo@kernel.org
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, peterz@infradead.org,
nicolas.pitre@linaro.org, tglx@linutronix.de,
daniel.lezcano@linaro.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched/idle: Reflow cpuidle_idle_call()
Date: Thu, 08 May 2014 13:41:29 +0200 [thread overview]
Message-ID: <5838571.inpi2giIZ5@vostro.rjw.lan> (raw)
In-Reply-To: <1877683.4pfeUuvFZ2@vostro.rjw.lan>
On Thursday, May 08, 2014 01:39:14 PM Rafael J. Wysocki wrote:
> On Thursday, May 08, 2014 03:47:40 AM tip-bot for Peter Zijlstra wrote:
> > Commit-ID: 37352273ad48f2d177ed1b06ced32d5536b773fb
> > Gitweb: http://git.kernel.org/tip/37352273ad48f2d177ed1b06ced32d5536b773fb
> > Author: Peter Zijlstra <peterz@infradead.org>
> > AuthorDate: Fri, 11 Apr 2014 13:55:48 +0200
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Thu, 8 May 2014 09:16:59 +0200
> >
> > sched/idle: Reflow cpuidle_idle_call()
> >
> > Apply goto to reduce lines and nesting levels.
>
> Well, I have a couple of patches that will conflict with this.
>
> This one in particular:
>
> https://patchwork.kernel.org/patch/4071541/
>
> which unfortunately already is in my linux-next branch, because I was
> unaware of this work.
>
> I wonder how we can resolve this?
And I wonder why I haven't been in the CC list of this tip-bot message even.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-05-08 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 10:47 tip-bot for Peter Zijlstra
2014-05-08 11:39 ` Rafael J. Wysocki
2014-05-08 11:41 ` Rafael J. Wysocki [this message]
2014-05-08 12:03 ` Peter Zijlstra
2014-05-08 11:56 ` Rafael J. Wysocki
2014-05-08 12:08 ` Peter Zijlstra
2014-05-08 16:33 ` Ingo Molnar
2014-05-08 16:49 ` Peter Zijlstra
2014-05-22 8:41 ` Ingo Molnar
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=5838571.inpi2giIZ5@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®