From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixup MODULE_DEVICE_TABLE(dmi, ...)
Date: Wed, 03 Dec 2008 09:03:21 +0000 [thread overview]
Message-ID: <1228295002.27314.6.camel@macbook.infradead.org> (raw)
In-Reply-To: <20081203004120.460166ac.akpm@linux-foundation.org>
On Wed, 2008-12-03 at 00:41 -0800, Andrew Morton wrote:
> The changelog is too crappy for me. Why did that error occur, and how
> does the patch fix it?
Well, you repeated the explanation of what's wrong -- although I don't
see how it actually causes an _error_; it works here.
The problem is that the MODULE_DEVICE_TABLE(dmi, foo) line expands to...
extern const struct dmi_device_id __mod_dmi_device_table
__attribute__ ((unused, alias("foo")));
And 'struct dmi_device_id' doesn't exist -- what we have is 'struct
dmi_system_id'.
In practice, this doesn't seem to matter because we never ask the
compiler to look _inside_ that struct -- it's just like a forward
declaration of 'struct foo' and then using pointers to it.
But it looks like Alexey's managed to find a way to actually make a
compiler barf on it, so that increases the motivation to fix it
promptly...
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-12-03 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:41 drivers/video/backlight/mbp_nvidia_bl.c:114: error: storage size of '__mod_dmi_device_table' isn't known Alexey Dobriyan
2008-11-15 11:14 ` David Woodhouse
2008-11-21 1:55 ` [PATCH] Fixup MODULE_DEVICE_TABLE(dmi, ...) Alexey Dobriyan
2008-12-03 8:41 ` Andrew Morton
2008-12-03 9:03 ` David Woodhouse [this message]
2008-12-03 22:56 ` Alexey Dobriyan
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=1228295002.27314.6.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome