From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>, Greg KH <greg@kroah.com>
Subject: Re: const vs __{dev}initdata
Date: Tue, 23 Oct 2007 18:10:25 -0400 [thread overview]
Message-ID: <471E7151.8070805@garzik.org> (raw)
In-Reply-To: <200710232335.56766.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> It seems that const cannot be (officialy) mixed with __{dev}initdata,
>
> include/linux/init.h:
> ...
> *
> * Also note, that this data cannot be "const".
> */
> ...
>
> [ BTW Greg: this doesn't seem to be mentioned in LDD3. ]
>
> Any reason for this limitation (other than not having .init.rodata section
> and __const__{dev}initdata tag)? There are places where we really would like
> to have both, i.e. struct ide_port_info in drivers/ide.
Thank you for asking this question... we really do need a solution for
this.
As you point out, there are many valid cases for both const and initdata.
Jeff
next prev parent reply other threads:[~2007-10-23 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 21:35 const vs __{dev}initdata Bartlomiej Zolnierkiewicz
2007-10-23 22:10 ` Jeff Garzik [this message]
2007-10-24 7:23 ` Geert Uytterhoeven
2007-10-24 3:33 ` Greg KH
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=471E7151.8070805@garzik.org \
--to=jeff@garzik.org \
--cc=bzolnier@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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