From: Chen Gang <gang.chen@asianux.com>
To: Hirokazu Takata <takata@linux-m32r.org>
Cc: linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: [PATCH] arch: m32r: include: asm: use 'readb' instead of 'read'
Date: Thu, 27 Jun 2013 10:57:34 +0800 [thread overview]
Message-ID: <51CBAA1E.8000206@asianux.com> (raw)
In-Reply-To: <51CBA43F.9050000@asianux.com>
Need use 'readb' instead of 'read', it is a typo issue which found by
compiler.
The related error (with allmodconfig):
drivers/i2c/busses/i2c-ocores.c: In function ‘oc_getreg_8’:
drivers/i2c/busses/i2c-ocores.c:96:2: error: implicit declaration of function ‘read’ [-Werror=implicit-function-declaration]
Signed-off-by: Chen Gang <gang.chen@asianux.com>
---
arch/m32r/include/asm/io.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/m32r/include/asm/io.h b/arch/m32r/include/asm/io.h
index 4010f1f..343ae4c 100644
--- a/arch/m32r/include/asm/io.h
+++ b/arch/m32r/include/asm/io.h
@@ -162,7 +162,7 @@ static inline void _writel(unsigned long l, unsigned long addr)
#define __raw_writew writew
#define __raw_writel writel
-#define ioread8 read
+#define ioread8 readb
#define ioread16 readw
#define ioread32 readl
#define iowrite8 writeb
--
1.7.7.6
next prev parent reply other threads:[~2013-06-27 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 2:32 [PATCH] arch: m32r: include: asm: add generic ioremap_wc() definition Chen Gang
2013-06-27 2:57 ` Chen Gang [this message]
2013-06-27 3:29 ` [PATCH] arch: m32r: include: asm: add ioread*be() and iowrite*be() Chen Gang
2013-06-27 4:37 ` [PATCH] arch: m32r: include: asm: add ioread*_rep() and iowrite*_rep() Chen Gang
2013-06-27 4:42 ` Chen Gang
2013-06-27 7:07 ` Geert Uytterhoeven
2013-06-27 8:25 ` Arnd Bergmann
2013-06-27 8:43 ` Geert Uytterhoeven
2013-06-28 2:19 ` Chen Gang
2013-06-27 8:55 ` Chen Gang
2013-06-27 9:28 ` Geert Uytterhoeven
2013-06-27 9:32 ` Chen Gang
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=51CBAA1E.8000206@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m32r-ja@ml.linux-m32r.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=takata@linux-m32r.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.