Re: Correct types for mod_devicetable.h (was: Re: m68k build failure)

On Sunday 02 December 2007 22:22:31 Geert Uytterhoeven wrote:
> On Sat, 1 Dec 2007, Pierre Ossman wrote:
> > Yeah, that could work. Have a header with stuff like this:
> >
> > typedef u16 __attribute__((aligned(2))) aligned_u16;
> > typedef u32 __attribute__((aligned(4))) aligned_u32;
>
> I gave it a try:

This seems to turn a molehill into a mountain.

We can change that mod_devicetable.h at any time; it's not supposed to be a 
userspace API (the kernel build system doesn't count).

So, just insert two bits of padding in sdio_device_id and insert a comment 
saying "/* Explicit padding: works even if we're cross-compiling */".

Thanks,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Correct types for mod_devicetable.h (was: Re: m68k build failure)
    • From: Adrian Bunk <[email protected]>

• References:
  • m68k build failure
    • From: Andrew Morton <[email protected]>
  • Re: m68k build failure
    • From: Pierre Ossman <[email protected]>
  • Correct types for mod_devicetable.h (was: Re: m68k build failure)
    • From: Geert Uytterhoeven <[email protected]>

• Prev by Date: Re: sched_yield: delete sysctl_sched_compat_yield
• Next by Date: Re: sched_yield: delete sysctl_sched_compat_yield
• Previous by thread: Correct types for mod_devicetable.h (was: Re: m68k build failure)
• Next by thread: Re: Correct types for mod_devicetable.h (was: Re: m68k build failure)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]