LKML Archive on
help / color / mirror / Atom feed
From: Andreas Schwab <>
To: Andrew Morton <>
Subject: Re: [PATCH] Fix hid_device_id for cross compiling
Date: Thu, 30 Oct 2008 10:19:51 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Andrew Morton's message of "Thu, 30 Oct 2008 00:23:32 -0700")

Andrew Morton <> writes:

> On Sun, 26 Oct 2008 00:30:18 +0200 Andreas Schwab <> wrote:
>> struct hid_device_id contains hidden padding which is bad for cross
>> compiling.  Make the padding explicit and consistent across
>> architectures.
> What is "bad" about it?

It is bad because it depends on the alignment restrictions of the
architecture.  On m68k everything is aligned on a 2-byte boundary, so
this padding does not exist.

> Can you expand a bit on the problem which is being fixed here?

It's the well known cross compiling problem with modpost that has bitten
us so often before.  This one is even worse, because modpost would
silently read bogus values since the struct size is the same, only the
padding moves elsewhere.


Andreas Schwab, SuSE Labs,
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."

      reply	other threads:[~2008-10-30  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 22:30 Andreas Schwab
2008-10-30  7:23 ` Andrew Morton
2008-10-30  9:19   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH] Fix hid_device_id for cross compiling' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).