From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: fix write*() I/O accessors
Date: Fri, 11 Feb 2011 23:51:54 +0100 [thread overview]
Message-ID: <4D55BD8A.201@ahsoftware.de> (raw)
In-Reply-To: <1297463148-6612-1-git-send-email-wd@denx.de>
Hello,
Am 11.02.2011 23:25, schrieb Wolfgang Denk:
> +#define writeb(v,c) ({ u8 __v = v; __iowmb(); __arch_putb(__v,c); __v; })
> +#define writew(v,c) ({ u16 __v = v; __iowmb(); __arch_putw(__v,c); __v; })
> +#define writel(v,c) ({ u32 __v = v; __iowmb(); __arch_putl(__v,c); __v; })
Thanks a lot, can I have the do {} while() back? I still don't like such
macro-making-sense-only constructs. (Just kidding). ;)
Regards,
Alexander
prev parent reply other threads:[~2011-02-11 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 22:25 [U-Boot] [PATCH] ARM: fix write*() I/O accessors Wolfgang Denk
2011-02-11 22:31 ` Albert ARIBAUD
2011-02-11 22:40 ` Wolfgang Denk
2011-02-11 22:51 ` Alexander Holler [this message]
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=4D55BD8A.201@ahsoftware.de \
--to=holler@ahsoftware.de \
--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