From: Kent Borg <kentborg@borg.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: IO, ANSI vs GCC structs
Date: Fri, 25 Jul 2003 13:47:34 -0400 [thread overview]
Message-ID: <20030725134734.J29161@borg.org> (raw)
In-Reply-To: <20030725161940.41FDEC602D@atlas.denx.de>; from wd@denx.de on Fri, Jul 25, 2003 at 06:19:35PM +0200
How important is it to the kernel coding style that hardware be
accessed through a structure? Is it acceptable to do:
#define MYHW (MY_MBAR+42)
...
out_be32(MYHW, 0xco1df00d);
?
Thanks,
-kb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-25 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 15:30 IO, ANSI vs GCC structs Kent Borg
2003-07-25 15:51 ` Bret Indrelee
2003-07-25 16:19 ` Wolfgang Denk
2003-07-25 17:47 ` Kent Borg [this message]
2003-07-25 19:22 ` Wolfgang Denk
2003-07-25 21:45 ` Paul Mackerras
[not found] <5.1.0.14.2.20030725123123.03855f58@mail.ebshome.net>
2003-07-25 19:59 ` Bret Indrelee
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=20030725134734.J29161@borg.org \
--to=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.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.