From: Pierre Ossman <drzeus@drzeus.cx>
To: Adrian Bunk <bunk@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Al Viro <viro@ftp.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Marcel Holtmann <marcel@holtmann.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-arch@vger.kernel.org
Subject: Re: Correct types for mod_devicetable.h (was: Re: m68k build failure)
Date: Mon, 10 Dec 2007 20:12:59 +0100 [thread overview]
Message-ID: <20071210201259.1ad466c7@poseidon.drzeus.cx> (raw)
In-Reply-To: <20071210181112.GM20441@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Mon, 10 Dec 2007 19:11:12 +0100
Adrian Bunk <bunk@kernel.org> wrote:
> On Sun, Dec 09, 2007 at 06:08:18PM +0100, Pierre Ossman wrote:
> >
> > This still requires a bit of maintenance to set up a kerneltypes.h for every arch.
>
> Better doing this work once than fixing similar issues again and again.
>
Agreed. But it raises the bar quite a bit to get this ready for upstream.
> > It also means we have to be very careful that gcc's internal alignment settings matched the ones in our header.
>
> There's nothing "gcc internal" about struct alignment - remember that
> any change in struct alignment would change our userspace ABI.
>
Oh? I would have guessed that everything going to and from userspace would be packed. Should probably consider myself lucky I have do deal with few such interactions. :)
Rgds
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-10 19:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 6:07 m68k build failure Andrew Morton
2007-11-28 8:48 ` Pierre Ossman
2007-11-28 9:00 ` Andrew Morton
2007-11-28 9:28 ` Al Viro
2007-11-28 12:29 ` Pierre Ossman
2007-11-28 12:34 ` Geert Uytterhoeven
2007-12-01 20:56 ` Pierre Ossman
2007-12-02 11:22 ` Correct types for mod_devicetable.h (was: Re: m68k build failure) Geert Uytterhoeven
2007-12-03 10:02 ` Rusty Russell
2007-12-08 21:58 ` Adrian Bunk
2007-12-09 6:43 ` Jon Masters
2007-12-09 17:10 ` Pierre Ossman
2007-12-12 1:34 ` Rusty Russell
2007-12-09 17:08 ` Pierre Ossman
2007-12-10 18:11 ` Adrian Bunk
2007-12-10 19:12 ` Pierre Ossman [this message]
2007-11-29 21:19 ` m68k build failure Andrew Morton
2007-11-30 17:55 ` Adrian Bunk
2007-11-28 9:24 ` Geert Uytterhoeven
2007-11-28 9:27 ` Geert Uytterhoeven
2007-11-28 10:01 ` Pierre Ossman
2007-11-28 10:07 ` Alan Cox
2007-11-28 10:23 ` Andreas Schwab
2007-11-28 9:58 ` Andreas Schwab
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=20071210201259.1ad466c7@poseidon.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®