From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/5] omap pm clean-up for v3.10 merge window
Date: Tue, 09 Apr 2013 23:52:29 +0200 [thread overview]
Message-ID: <51648D9D.5000204@linaro.org> (raw)
In-Reply-To: <87mwt71imz.fsf@linaro.org>
On 04/09/2013 11:47 PM, Kevin Hilman wrote:
> Daniel Lezcano <daniel.lezcano@linaro.org> writes:
>
> [...]
>
>>>>>>>
>>>>>>> PM cleanup to prepare for omap5 PM via Kevin Hilman <khilman@linaro.org>:
>>>>>>>
>>>>>>> OMAP3/4 CPUidle cleanups for v3.10
>>>>>>
>>>>>> Adding Daniel and Rafael to Cc.
>>
>> Kevin,
>>
>> I just want to point you this patch:
>>
>> https://git.linaro.org/gitweb?p=people/dlezcano/cpuidle-next.git;a=commit;h=e03a37fdf942a25154ccb5539524afd336f130bb
>>
>> I did not yet send it to Rafael.
>
> I haven't seen that one posted anywhere so it's not in my queue, and
> probably too late for v3.10.
>
> Once it's posted, I'll queue it up, and we can maybe get it in for
> v3.10-rc.
Yes, I just did the fix very recently. It was just a head up. I will
send it to Rafael as soon as the 'bleeding edge' branch is merged with
'linux-next'.
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-04-09 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0MarPy-1U9XGk2D8s-00Ks1o@mx.kundenserver.de>
2013-04-09 14:52 ` [GIT PULL 2/5] omap pm clean-up for v3.10 merge window Arnd Bergmann
2013-04-09 16:38 ` Kevin Hilman
2013-04-09 16:56 ` Tony Lindgren
2013-04-09 17:36 ` Kevin Hilman
2013-04-09 21:03 ` Daniel Lezcano
2013-04-09 21:47 ` Kevin Hilman
2013-04-09 21:52 ` Daniel Lezcano [this message]
2013-04-09 4:51 [GIT PULL 1/5] omap pm fixes " Tony Lindgren
2013-04-09 4:51 ` [GIT PULL 2/5] omap pm clean-up " Tony Lindgren
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=51648D9D.5000204@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).