From: Jiri Slaby <jirislaby@gmail.com>
To: Bryan Wu <cooloney@kernel.org>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org, wim@iguana.be,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH 1/1] Blackfin char driver for Blackfin on-chip OTP memory (v3)
Date: Thu, 27 Mar 2008 12:09:04 +0100 [thread overview]
Message-ID: <47EB8050.4010700@gmail.com> (raw)
In-Reply-To: <1206643758-9319-1-git-send-email-cooloney@kernel.org>
Bryan Wu napsal(a):
> From: Mike Frysinger <vapier.adi@gmail.com>
>
> initial char driver for otp memory
> (only read supported atm ... needs real examples/docs for write support)
>
> v2-v3:
> - fixup __initdata with __initconst, as we are heading for 2.6.26
OK, thanks.
> Signed-off-by: Mike Frysinger <vapier.adi@gmail.com>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
Acked-by: Jiri Slaby <jirislaby@gmail.com>
Will somebody pick the patch up (otherwise cc akpm or I might fwd it)?
next prev parent reply other threads:[~2008-03-27 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 18:49 [PATCH 1/1] Blackfin char driver for Blackfin on-chip OTP memory (v3) Bryan Wu
2008-03-27 11:09 ` Jiri Slaby [this message]
2008-03-27 12:09 ` Mike Frysinger
2008-03-27 12:10 ` Jiri Slaby
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=47EB8050.4010700@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