From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
len.brown@intel.com, Paul Bristow <paul@paulbristow.net>,
mpm@selenic.com, B.Zolnierkiewicz@elka.pw.edu.pl, kkeil@suse.de,
linux-dvb-maintainer@linuxtv.org, philb@gnu.org, gregkh@suse.de,
dwmw2@infradead.org
Subject: Re: kbuild: Section mismatch warnings
Date: Fri, 17 Feb 2006 19:49:26 -0500 [thread overview]
Message-ID: <200602171949.27532.dtor_core@ameritech.net> (raw)
In-Reply-To: <20060217224702.GA25761@mars.ravnborg.org>
On Friday 17 February 2006 17:47, Sam Ravnborg wrote:
> Several warnings are refereces to module parameters - sound/oss/mad16.o
> as the most visible one. I have not yet figured out if this is a false
> positive or not. Removing __initdata on the moduleparam variable solves
> it, but then this may be the wrong approach.
>
It looks like your check does not like when data associated with a module
parameter is marked __initdata. But I think it is allowed as long as
module parameter access mode is 0 so we don't create sysfs entry for it.
--
Dmitry
next prev parent reply other threads:[~2006-02-18 0:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 21:48 kbuild: Sam Ravnborg
2006-02-17 22:47 ` kbuild: Section mismatch warnings Sam Ravnborg
2006-02-17 23:32 ` Adrian Bunk
2006-02-17 23:38 ` Sam Ravnborg
2006-02-17 23:56 ` Adrian Bunk
2006-02-18 0:14 ` Nicholas Miell
2006-02-18 21:25 ` Sam Ravnborg
2006-02-18 0:09 ` Greg KH
2006-02-18 0:48 ` David Brownell
2006-02-18 0:57 ` Greg KH
2006-02-18 20:32 ` David Brownell
2006-02-19 0:21 ` Sam Ravnborg
2006-02-22 5:09 ` Greg KH
2006-02-18 0:49 ` Dmitry Torokhov [this message]
2006-02-18 12:14 ` Sam Ravnborg
2006-02-18 13:34 ` Russell King
2006-02-19 11:36 ` Sam Ravnborg
2006-02-19 12:59 ` [v4l-dvb-maintainer] " Johannes Stezenbach
2006-02-19 13:19 ` Sam Ravnborg
2006-02-19 13:30 ` Johannes Stezenbach
2006-02-25 15:31 ` Adrian Bunk
2006-02-19 14:18 ` Sam Ravnborg
2006-02-19 22:38 ` Rusty Russell
2006-02-19 22:44 ` Sam Ravnborg
2006-02-18 22:12 ` kbuild: Andi Kleen
2006-02-18 22:38 ` kbuild: Sam Ravnborg
2006-02-18 23:41 ` kbuild: Sam Ravnborg
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=200602171949.27532.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=kkeil@suse.de \
--cc=len.brown@intel.com \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paul@paulbristow.net \
--cc=philb@gnu.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