From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Andre Przywara <andre.przywara@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM : cpuidle: 3.13 fix
Date: Tue, 31 Dec 2013 22:30:39 +0100 [thread overview]
Message-ID: <4735745.5h2OjxOOl8@vostro.rjw.lan> (raw)
In-Reply-To: <52C15268.4050403@linaro.org>
On Monday, December 30, 2013 12:00:56 PM Daniel Lezcano wrote:
> Hi Rafael,
>
> this pull request provides a single fix for the calxeda cpuidle driver.
> It is based on v3.13-rc6.
>
> * Andre Przywara fixed a compilation warning due to the driver probe
> function prototype mismatch for the calxeda cpuidle driver
>
> Thanks
> -- Daniel
>
> The following changes since commit 802eee95bde72fd0cd0f3a5b2098375a487d1eda:
>
> Linux 3.13-rc6 (2013-12-29 16:01:33 -0800)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/daniel.lezcano/linux.git cpuidle/3.13-fixes
>
> for you to fetch changes up to 5781532ebecd9e0b7b5fc25d78030bdec635f4ac:
>
> ARM/cpuidle: remove __init tag from Calxeda cpuidle probe function
> (2013-12-30 11:55:20 +0100)
>
> ----------------------------------------------------------------
> Andre Przywara (1):
> ARM/cpuidle: remove __init tag from Calxeda cpuidle probe function
>
> drivers/cpuidle/cpuidle-calxeda.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Pulled and pushed out (into the fixes branch).
Thanks and Happy New Year!
Rafael
prev parent reply other threads:[~2013-12-31 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 11:00 Daniel Lezcano
2013-12-30 11:02 ` [PATCH] ARM/cpuidle: remove __init tag from Calxeda cpuidle probe function Daniel Lezcano
2013-12-31 21:30 ` Rafael J. Wysocki [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=4735745.5h2OjxOOl8@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=andre.przywara@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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®