From: Alan Modra <amodra@bigpond.net.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc64-dev <linuxppc64-dev@ozlabs.org>, ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC][PATCH] combining header files
Date: Wed, 9 Mar 2005 11:49:29 +1030 [thread overview]
Message-ID: <20050309011929.GI15642@bubble.modra.org> (raw)
In-Reply-To: <20050309120343.0c22eb0f.sfr@canb.auug.org.au>
On Wed, Mar 09, 2005 at 12:03:43PM +1100, Stephen Rothwell wrote:
> I would just like to start a discussion about consolidating (some of) the
> ppc and ppc64 header files.
Marvellous! In case it isn't completely obvious, you can often share
structure definitions between ppc32 and ppc64 by judicious selection of
types. eg.
struct stays_the_same {
long long some_64bit_var;
int some_32bit_var;
}
struct bigger_in_64bit {
long var_sized_by_arch;
}
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-03-09 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 1:03 [RFC][PATCH] combining header files Stephen Rothwell
2005-03-09 1:19 ` Alan Modra [this message]
2005-03-09 9:40 ` Geert Uytterhoeven
2005-03-09 12:06 ` Alan Modra
2005-03-09 20:01 ` Linas Vepstas
2005-03-10 2:42 ` Stephen Rothwell
2005-03-14 19:36 ` Linas Vepstas
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=20050309011929.GI15642@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.