From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: mitr@volny.cz, linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/input/misc/wistron_btns.c: section fixes
Date: Mon, 26 Jun 2006 10:10:16 -0400 [thread overview]
Message-ID: <d120d5000606260710g5f93773fuf7b94d85830fbed5@mail.gmail.com> (raw)
In-Reply-To: <200606260750.32863.dtor_core@ameritech.net>
On 6/26/06, Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> On Monday 26 June 2006 06:35, Adrian Bunk wrote:
> > This patch contains the following fixes:
> > - it doesn't make sense to mark a variable on the stack as __initdata
> > - struct dmi_ids is using the __init dmi_matched()
>
> Since when did static variables become allocated on stack?
>
BTW, if I add __intidata to dmi_ids array GCC (3.4.4) bitches at me:
CC drivers/input/misc/wistron_btns.o
drivers/input/misc/wistron_btns.c:345: error: dmi_ids causes a section
type conflict
make[1]: *** [drivers/input/misc/wistron_btns.o] Error 1
make: *** [drivers/input/misc/] Error 2
I have to declare it as "static const struct dmi_system_id __initdata
dmi_ids[] = {..." for it to compile successfully, but there is a
comment that we should not use const with __initdata. Although I
checked the assembly oputput and const __initdata endes up in
init.data section - exactly where we want it. Wierd...
--
Dmitry
next prev parent reply other threads:[~2006-06-26 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 10:35 Adrian Bunk
2006-06-26 11:50 ` Dmitry Torokhov
2006-06-26 14:10 ` Dmitry Torokhov [this message]
2006-06-29 16:49 ` Adrian Bunk
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=d120d5000606260710g5f93773fuf7b94d85830fbed5@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=bunk@stusta.de \
--cc=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mitr@volny.cz \
/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®