From: Andreas Schwab <schwab@suse.de>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
Marcel Holtmann <marcel@holtmann.org>,
linux-kernel@vger.kernel.org
Subject: Re: m68k build failure
Date: Wed, 28 Nov 2007 10:58:45 +0100 [thread overview]
Message-ID: <jeve7m3d4a.fsf@sykes.suse.de> (raw)
In-Reply-To: <20071128094856.056c0a3f@poseidon.drzeus.cx> (Pierre Ossman's message of "Wed\, 28 Nov 2007 09\:48\:56 +0100")
Pierre Ossman <drzeus@drzeus.cx> writes:
> On Tue, 27 Nov 2007 22:07:23 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
>>
>> Current Linus tree give me this, with m68k allmodconfig:
>>
>> FATAL: drivers/bluetooth/btsdio: sizeof(struct sdio_device_id)=12 is not a modulo of the size of section __mod_sdio_device_table=30.
>> Fix definition of struct sdio_device_id in mod_devicetable.h
>>
>> which I haven't seen before. Any ideas?
>>
>
> No the slightest. 12 seems like the correct, padded size. A size of 10 is just weird as the unpadded size is 9 bytes. Could you dump the __mod_sdio_device_table section so we can determine if it is cropped or just oddly padded.
A size of 10 is correct. On m68k no type is aligned to more than 2
bytes.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2007-11-28 9:59 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
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 [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=jeve7m3d4a.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).