From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP: misc. fixes for 2.6.32
Date: Fri, 28 Aug 2009 09:00:49 -0700 [thread overview]
Message-ID: <20090828160049.GI25828@atomide.com> (raw)
In-Reply-To: <1251448127-27336-1-git-send-email-khilman@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [090828 01:28]:
> Tony,
>
> I pushed a couple more fixes to my pm-upstream/fixes-32 branch. You've
> already pulled this branch into your for-next, so a re-pull will get
> you just these two additional patches.
OK, I need to rebuild the omap for-next as there are few compilation
issues in at least the omap3-upstream series.
Regards,
Tony
> Thanks,
>
> Kevin
>
>
> Reddy, Teerth (1):
> OMAP3: PM: add T2 interrupt line mux setting, and enable on 3430SDP
>
> Vikram Pandita (1):
> OMAP: Zoom2: release debug board detect gpio line
>
> arch/arm/mach-omap2/board-3430sdp.c | 6 ++++++
> arch/arm/mach-omap2/board-zoom-debugboard.c | 7 ++++---
> arch/arm/mach-omap2/mux.c | 5 +++++
> arch/arm/plat-omap/include/mach/mux.h | 3 +++
> 4 files changed, 18 insertions(+), 3 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-08-28 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 8:28 [PATCH 0/2] OMAP: misc. fixes for 2.6.32 Kevin Hilman
2009-08-28 8:28 ` [PATCH 1/2] OMAP3: PM: add T2 interrupt line mux setting, and enable on 3430SDP Kevin Hilman
2009-08-28 8:28 ` [PATCH 2/2] OMAP: Zoom2: release debug board detect gpio line Kevin Hilman
2009-08-28 16:00 ` Tony Lindgren [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=20090828160049.GI25828@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).