From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Paul Rusty Russel <rusty@rustcorp.com.au>
Subject: Re: 2.4.4-ac6 compile error in plip.c
Date: Fri, 11 May 2001 10:03:12 +0200 [thread overview]
Message-ID: <20010511100312.V754@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3AFA9BC3.1060207@surfbest.net> <2514.989556789@kao2.melbourne.sgi.com>
In-Reply-To: <2514.989556789@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Fri, May 11, 2001 at 02:53:09PM +1000
On Fri, May 11, 2001 at 02:53:09PM +1000, Keith Owens wrote:
> The first __initdata is marked as const, the second is not, a section
> cannot contain both const and non-const data. Against 2.4.4-ac6.
So we should also update the documentation to reflect this.
--- linux-2.4.4/include/linux/init.h.orig Wed May 9 21:33:38 2001
+++ linux-2.4.4/include/linux/init.h Fri May 11 09:53:57 2001
@@ -34,6 +34,8 @@
* Don't forget to initialize data not at file scope, i.e. within a function,
* as gcc otherwise puts the data into the bss section and not into the init
* section.
+ *
+ * Also note, that this data cannot be "const".
*/
#ifndef MODULE
--- linux-2.4.4/Documentation/DocBook/kernel-hacking.tmpl.orig Fri Apr 6 19:42:55 2001
+++ linux-2.4.4/Documentation/DocBook/kernel-hacking.tmpl Fri May 11 09:58:45 2001
@@ -713,7 +713,8 @@
</para>
<para>
Static data structures marked as <type>__initdata</type> must be initialised
- (as opposed to ordinary static data which is zeroed BSS).
+ (as opposed to ordinary static data which is zeroed BSS) and cannot be
+ <type>const</type>.
</para>
</sect1>
Regards
Ingo Oeser
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
prev parent reply other threads:[~2001-05-11 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 13:46 Moses McKnight
2001-05-11 4:53 ` Keith Owens
2001-05-11 8:03 ` Ingo Oeser [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:
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=20010511100312.V754@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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®