From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v2.6.38-rc2
Date: Mon, 31 Jan 2011 10:04:56 -0800 [thread overview]
Message-ID: <20110131180456.GA3358@atomide.com> (raw)
Hi Linus,
Please pull some omap fixes from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-fixes-for-linus
This is mostly to fix few compiler warning that sneaked in during the
merge window. Also included is one trivial omap1 related cleanup patch
to keep the code consistent with omap2+, and one PTR_ERR fix.
Regards,
Tony
The following changes since commit 6fb1b304255efc5c4c93874ac8c066272e257e28:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input (2011-01-26 16:31:44 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-fixes-for-linus
Felipe Balbi (1):
arm: omap2: mux: fix compile warning
Julia Lawall (1):
arch/arm/mach-omap2/dma.c: Convert IS_ERR result to PTR_ERR
Russell King (1):
omap2+: Fix unused variable warning for omap_irq_base
Tony Lindgren (1):
omap1: Simplify use of omap_irq_flags
arch/arm/mach-omap1/include/mach/entry-macro.S | 13 -------------
arch/arm/mach-omap1/irq.c | 2 +-
arch/arm/mach-omap2/dma.c | 2 +-
arch/arm/mach-omap2/include/mach/entry-macro.S | 14 --------------
arch/arm/mach-omap2/io.c | 6 ++----
arch/arm/mach-omap2/mux.c | 2 +-
6 files changed, 5 insertions(+), 34 deletions(-)
next reply other threads:[~2011-01-31 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 18:04 Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-24 17:40 [GIT PULL] omap fixes for v2.6.38-rc2 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=20110131180456.GA3358@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).