From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP: Few sparse/bug fixes and clean-up for 3.2
Date: Wed, 28 Sep 2011 15:12:51 -0700 [thread overview]
Message-ID: <20110928221251.GF6324@atomide.com> (raw)
In-Reply-To: <1316852520-10377-1-git-send-email-santosh.shilimkar@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [110924 00:48]:
> Tony,
>
> Please pull few OMAP sparse/bug fixes and clean-up for 3.2
Thanks I'll pull these into l3 branch for v3.2 merge window and
merge them into l-o master.
Tony
> Thnaks,
> Santosh
>
> The following changes since commit b6fd41e29dea9c6753b1843a77e50433e6123bcb:
>
> Linux 3.1-rc6 (2011-09-12 14:02:02 -0700)
>
> are available in the git repository at:
> git://gitorious.org/omap-sw-develoment/linux-omap-dev.git for_3_2/omap_misc
>
> Santosh Shilimkar (1):
> OMAP4: Fix the emif and dmm virtual mapping
>
> Todd Poynor (2):
> OMAP: Improve register access in L3 Error handler.
> OMAP: Fix a BUG in l3 error handler.
>
> sricharan (3):
> OMAP: Fix indentation issues in l3 error handler.
> OMAP: Fix sparse warnings in l3 error handler.
> OMAP: Print Initiator name for l3 custom error.
>
> arch/arm/mach-omap2/omap_l3_noc.c | 130 ++++++++++----------
> arch/arm/mach-omap2/omap_l3_noc.h | 224 +++++++++++++++++++---------------
> arch/arm/mach-omap2/omap_l3_smx.c | 91 +++++++-------
> arch/arm/mach-omap2/omap_l3_smx.h | 164 ++++++++++++------------
> arch/arm/plat-omap/include/plat/io.h | 4 +-
> 5 files changed, 322 insertions(+), 291 deletions(-)
prev parent reply other threads:[~2011-09-28 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 8:22 [GIT PULL] OMAP: Few sparse/bug fixes and clean-up for 3.2 Santosh Shilimkar
2011-09-28 22:12 ` 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=20110928221251.GF6324@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).