From: Bryan Wu <cooloney@kernel.org>
To: felipe.balbi@nokia.com, linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Bryan Wu <cooloney@kernel.org>
Subject: [PATCH 2/4] usb: musb: Blackfin provides read/write I/O accessor in header files
Date: Mon, 10 Nov 2008 11:25:13 +0800 [thread overview]
Message-ID: <1226287515-27247-3-git-send-email-cooloney@kernel.org> (raw)
In-Reply-To: <1226287515-27247-1-git-send-email-cooloney@kernel.org>
Don't redefine the functions in musb driver
Signed-off-by: Bryan Wu <cooloney@kernel.org>
---
drivers/usb/musb/musb_io.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/musb/musb_io.h b/drivers/usb/musb/musb_io.h
index 15f0577..b06e9ef 100644
--- a/drivers/usb/musb/musb_io.h
+++ b/drivers/usb/musb/musb_io.h
@@ -39,7 +39,7 @@
#if !defined(CONFIG_ARM) && !defined(CONFIG_SUPERH) \
&& !defined(CONFIG_AVR32) && !defined(CONFIG_PPC32) \
- && !defined(CONFIG_PPC64)
+ && !defined(CONFIG_PPC64) && !defined(CONFIG_BLACKFIN)
static inline void readsl(const void __iomem *addr, void *buf, int len)
{ insl((unsigned long)addr, buf, len); }
static inline void readsw(const void __iomem *addr, void *buf, int len)
--
1.5.6.3
next prev parent reply other threads:[~2008-11-10 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 3:25 [PATCH 0/4] usb/musb Blackfin updates Bryan Wu
2008-11-10 3:25 ` [PATCH 1/4] usb: musb: add Blackfin specific configuration to MUSB (add missing file changes) Bryan Wu
2008-11-10 3:25 ` Bryan Wu [this message]
2008-11-10 3:25 ` [PATCH 3/4] usb: musb: Kill some compiling warning in musb Blackfin part Bryan Wu
2008-11-10 3:25 ` [PATCH 4/4] usb: musb: use static inline functions to replace the macros in Blackfin version Bryan Wu
2008-11-13 3:01 ` [PATCH 0/4] usb/musb Blackfin updates Bryan Wu
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=1226287515-27247-3-git-send-email-cooloney@kernel.org \
--to=cooloney@kernel.org \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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