From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Non critical fixes for v3.3 merge window, part2
Date: Mon, 19 Dec 2011 12:23:54 -0800 [thread overview]
Message-ID: <20111219202354.GA17267@atomide.com> (raw)
In-Reply-To: <20111219194546.GP6464@atomide.com>
Resending with mailing lists in Cc.
* Tony Lindgren <tony@atomide.com> [111219 11:45]:
> Hi Arnd & Olof,
>
> Please pull few non-critical fixes for v3.3 merge window from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes-non-critical-part2
>
> These will be needed for some omap hwmod and ehci changes I'll
> post pull requests for after this. Note that this is based on
> the earlier pull request for fixes, so those two fixes will also
> get pulled in if they don't make it to the -rc cycle.
>
> Regards,
>
> Tony
>
>
> The following changes since commit 4a4de1d9b47156525ceb46c7faf6ae4042d90aa7:
> Tony Lindgren (1):
> Merge branch 'hwmod_data_fixes_3.2rc' of git://git.pwsan.com/linux-2.6 into fixes-hwmod
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes-non-critical-part2
>
> Benoit Cousson (1):
> ARM: OMAP4: hwmod: Don't wait for the idle status if modulemode is not supported
>
> Paul Walmsley (1):
> ARM: OMAP: AM3517/3505: fix crash on boot due to incorrect voltagedomain data
>
> Santosh Shilimkar (1):
> ARM: OMAP4: clock: Add CPU local timer clock node
>
> arch/arm/mach-omap2/clock44xx_data.c | 9 ++
> arch/arm/mach-omap2/omap_hwmod.c | 98 ++++++++++++------------
> arch/arm/mach-omap2/voltagedomains3xxx_data.c | 40 +++++++++--
> 3 files changed, 92 insertions(+), 55 deletions(-)
next parent reply other threads:[~2011-12-19 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111219194546.GP6464@atomide.com>
2011-12-19 20:23 ` Tony Lindgren [this message]
2011-12-22 17:27 ` [GIT PULL] Non critical fixes for v3.3 merge window, part2 Olof Johansson
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=20111219202354.GA17267@atomide.com \
--to=tony@atomide.com \
--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).