From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm:io.h: define __io() macro if not defined erlier
Date: Wed, 19 May 2010 16:34:50 +0200 [thread overview]
Message-ID: <4BF3F70A.4020204@gmail.com> (raw)
In-Reply-To: <1274259427-29386-1-git-send-email-biessmann@corscience.de>
Hello,
there is a typo in comment -> earlier.
Am 19.05.2010 10:57, schrieb Andreas Bie?mann:
> This patch adds __io() macro to enable {in|out}[bwl] macros in
> arch/arm/asm/io.h
>
> Commit a45dde2293c816138e53c26eca6fd0322583f9a6 uses {in|out}[bwl] macros in
> DM9000x and breaks compilation for arm devices.
>
> Signed-off-by: Andreas Bie?mann <biessmann@corscience.de>
> ---
> arch/arm/include/asm/io.h | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/include/asm/io.h b/arch/arm/include/asm/io.h
> index 0a4b5be..ccbf80d 100644
> --- a/arch/arm/include/asm/io.h
> +++ b/arch/arm/include/asm/io.h
> @@ -173,6 +173,13 @@ extern void __raw_readsl(unsigned int addr, void *data, int longlen);
> #if 0 /* XXX###XXX */
> #include <asm/arch/io.h>
> #endif /* XXX###XXX */
> +/*
> + * we need to define __io(p) for {in,out}[bwl] macros. This macro may be
> + * defined in a machine specific io definition earlier.
> + */
> +#ifndef __io
> +#define __io(p) (p)
> +#endif
>
> /*
> * IO port access primitives
I tested it on Devkit8000.
Tested-by: Thomas Weber <weber@corscience.de>
next prev parent reply other threads:[~2010-05-19 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 8:57 [U-Boot] [PATCH] arm:io.h: define __io() macro if not defined erlier Andreas Bießmann
2010-05-19 14:34 ` Thomas Weber [this message]
2010-05-21 21:07 ` Wolfgang Denk
2010-05-25 8:15 ` Andreas Bießmann
2010-05-25 11:29 ` Wolfgang Denk
2010-05-26 9:49 ` Andreas Bießmann
2010-05-26 17:50 ` Mike Frysinger
2010-05-26 20:19 ` Wolfgang Denk
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=4BF3F70A.4020204@gmail.com \
--to=thomas.weber.linux@googlemail.com \
--cc=u-boot@lists.denx.de \
/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