From: Jiri Slaby <jirislaby@gmail.com>
To: Bryan Wu <cooloney@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>,
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 11:33:51 +0100 [thread overview]
Message-ID: <47EA268F.8070006@gmail.com> (raw)
In-Reply-To: <1206580131-22527-1-git-send-email-cooloney@kernel.org>
On 03/27/2008 02:08 AM, Bryan Wu wrote:
> From: Mike Frysinger <vapier.adi@gmail.com>
>
> initial char driver for otp memory
> (only read supported atm ... needs real examples/docs for write support)
>
> Signed-off-by: Mike Frysinger <vapier.adi@gmail.com>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
Nice,
Acked-by: Jiri Slaby <jirislaby@gmail.com>
> diff --git a/drivers/char/bfin-otp.c b/drivers/char/bfin-otp.c
> new file mode 100644
> index 0000000..2edc284
> --- /dev/null
> +++ b/drivers/char/bfin-otp.c
[...]
> +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).
next prev parent reply other threads:[~2008-03-26 10: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 [this message]
2008-03-26 14:31 ` Mike Frysinger
2008-03-26 18:34 ` Jiri Slaby
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=47EA268F.8070006@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