From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Cc: linux@arm.linux.org.uk, jarkko.nikula@nokia.com
Subject: [PATCH v3 0/2] OMAP2xxx EAC build fix and sparse cleanup
Date: Fri, 05 Sep 2008 01:37:14 -0600 [thread overview]
Message-ID: <20080905073522.7741.76584.stgit@localhost.localdomain> (raw)
This series fixes a build bug in the EAC driver after the recent IO address
changes, and resolves some sparse warnings. Updated to use ioremap().
Thanks to Jarkko Nikula <jarkko.nikula@nokia.com> for testing and Russell
King <linux@arm.linux.org.uk> for review.
Compile-tested only.
- Paul
---
arch/arm/mach-omap2/devices.c | 4 ++--
sound/arm/omap/eac.c | 8 +++++---
2 files changed, 7 insertions(+), 5 deletions(-)
next reply other threads:[~2008-09-05 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 7:37 Paul Walmsley [this message]
2008-09-05 7:37 ` [PATCH v3 1/2] OMAP2xxx EAC: update per recent IO address changes Paul Walmsley
2008-09-05 7:37 ` [PATCH v3 2/2] OMAP2xxx EAC: fix sparse warnings Paul Walmsley
2008-09-05 18:28 ` [PATCH v3 0/2] OMAP2xxx EAC build fix and sparse cleanup 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=20080905073522.7741.76584.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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