public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dave Jones <davej@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] const initdata.
Date: Fri, 24 Aug 2001 17:26:29 +0200	[thread overview]
Message-ID: <3B867225.5010008@fugmann.dhs.org> (raw)
In-Reply-To: <E15aIjC-0005vy-00@the-village.bc.nu>

Ah.. I misread the first posting.

Then we are down to zero .h and 43 .c files that are affected.
(a total of 121 lines containing 'const' before '__initdata')

Can these be fixed without testing (ie. through a script).
If so, I'm willing to post a patch.

Regards
Anders Fugmann





Alan Cox wrote:
>>How "bad" is it to have __initdata declared static?
>>
> 
> static is fine as it just changes name scoping, const however can try and
> put data in other places such as code segments. That breaks stuff when
> compiling with certain gcc versions
> 
> 



      reply	other threads:[~2001-08-24 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23 23:55 [PATCH] const initdata Dave Jones
2001-08-24 15:00 ` Anders Peter Fugmann
2001-08-24 15:18   ` Alan Cox
2001-08-24 15:26     ` Anders Peter Fugmann [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=3B867225.5010008@fugmann.dhs.org \
    --to=afu@fugmann.dhs.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@suse.de \
    --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