From: Jiri Slaby <jirislaby@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Bryan Wu <cooloney@kernel.org>,
linux-kernel@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/1] [Blackfin try #2] char driver for Blackfin on-chip OTP memory
Date: Wed, 26 Mar 2008 19:34:03 +0100 [thread overview]
Message-ID: <47EA971B.1020502@gmail.com> (raw)
In-Reply-To: <8bd0f97a0803260731x4378c71q1e2e5598c1728e1d@mail.gmail.com>
On 03/26/2008 03:31 PM, Mike Frysinger wrote:
> On Wed, Mar 26, 2008 at 6:33 AM, Jiri Slaby <jirislaby@gmail.com> wrote:
>> On 03/27/2008 02:08 AM, Bryan Wu wrote:
>> > From: Mike Frysinger <vapier.adi@gmail.com>
>>> +static int __init bfin_otp_init(void)
>> > +{
>> > + int ret;
>> > +
>> > + stampit();
>> > +
>> > + ret = misc_register(&bfin_otp_misc_device);
>> > + if (ret) {
>> > + pr_init(KERN_ERR PFX "unable to register a misc device\n");
>> > + return ret;
>> > + }
>> > +
>> > + pr_init(KERN_INFO PFX "initialized\n");
>>
>> except the fact, that pr_init definition seems to be broken. Its defined __fmt
>> is const, so it should reside in .init.rodata (__initconst), not .init.data
>> (__initdata).
>
> i dont see an __initconst macro anywhere ?
It's in include/linux/init.h as of 2.6.25-rc2.
> also, it isnt "broken" in the sense that it "doesnt work" ;)
Gcc simply doesn't allow that, you likely got 2 sections with init.data, with
and without readonly bit set, which is wrong, and it seems, that on some systems
(debian) you won't even compile it.
next prev parent reply other threads:[~2008-03-26 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 1:08 [PATCH 1/1] [Blackfin try #2] char driver for Blackfin on-chip OTP memory Bryan Wu
2008-03-26 10:33 ` Jiri Slaby
2008-03-26 14:31 ` Mike Frysinger
2008-03-26 18:34 ` Jiri Slaby [this message]
2008-03-26 18:40 ` Mike Frysinger
2008-03-26 19:09 ` Sam Ravnborg
2008-03-26 19:14 ` Mike Frysinger
2008-03-26 21:08 ` Sam Ravnborg
2008-03-26 21:12 ` Mike Frysinger
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=47EA971B.1020502@gmail.com \
--to=jirislaby@gmail.com \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vapier.adi@gmail.com \
--cc=wim@iguana.be \
/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