From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org, kernel@pengutronix.de
Subject: Re: [PATCH v2] mtdchar: handle chips that have user otp but no factory otp
Date: Wed, 6 Mar 2013 09:51:48 +0100 [thread overview]
Message-ID: <20130306085148.GS22886@pengutronix.de> (raw)
In-Reply-To: <1362559625.21850.17.camel@sauron>
On Wed, Mar 06, 2013 at 10:47:05AM +0200, Artem Bityutskiy wrote:
> On Mon, 2013-03-04 at 17:35 +0100, Uwe Kleine-König wrote:
> > Before this patch mtd_read_fact_prot_reg was used to check availability
> > for both MTD_OTP_FACTORY and MTD_OTP_USER access. This made accessing
> > user otp for chips that don't have a factory otp area impossible. So use
> > the right wrapper depending on the intended area to be accessed.
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > Forwarded: id:1361182768-31919-1-git-send-email-u.kleine-koenig@pengutronix.de
>
> Pushed to l2-mtd.git, thanks.
>
> I've removed the "Forwarded:" tag since I've never seen these to be used
> before and not sure if this is an agreed practice.
We use this internally at Pengutronix to keep track of what is already
sent. Usually I remove the tag before resubmission.
Having said that I think it doesn't hurt and tip documents the message
id, too. But there are more urgent problems to solve and I'm fine with
dropping the tag.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2013-03-06 8:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 10:19 [PATCH] mtdchar: handle chips that have user otp but no factory otp Uwe Kleine-König
2013-03-02 15:41 ` Artem Bityutskiy
2013-03-02 21:08 ` Uwe Kleine-König
2013-03-04 16:35 ` [PATCH v2] " Uwe Kleine-König
2013-03-04 16:47 ` [PATCH v2] mtd/nand: don't use {read,write}_buf for 8-bit transfers Uwe Kleine-König
2013-03-04 16:50 ` Uwe Kleine-König
2013-03-05 2:00 ` [PATCH v2] mtd/nand: don't use {read, write}_buf " Huang Shijie
2013-03-13 9:33 ` [PATCH v2] mtd/nand: don't use {read,write}_buf " Artem Bityutskiy
2013-11-26 21:03 ` Uwe Kleine-König
2013-11-27 6:59 ` Brian Norris
2013-03-13 10:26 ` Artem Bityutskiy
2013-04-05 12:13 ` David Woodhouse
2013-11-26 21:15 ` [PATCH v3] " Uwe Kleine-König
2013-11-27 7:35 ` Brian Norris
2013-11-29 12:20 ` Ezequiel Garcia
2013-11-30 6:04 ` Brian Norris
2013-11-30 11:19 ` Ezequiel Garcia
2013-11-30 16:35 ` Ezequiel Garcia
2013-11-30 16:51 ` Ezequiel Garcia
2013-11-30 19:01 ` Brian Norris
2013-11-30 21:06 ` Ezequiel Garcia
2013-12-02 19:40 ` Gupta, Pekon
2013-11-30 18:53 ` Brian Norris
2013-11-30 20:57 ` Ezequiel Garcia
2013-12-05 21:22 ` [PATCH v4] " Uwe Kleine-König
2013-12-17 5:48 ` Brian Norris
2013-12-17 21:46 ` Ezequiel Garcia
2013-12-19 7:39 ` Brian Norris
2014-01-14 8:12 ` Brian Norris
2014-01-14 8:29 ` Uwe Kleine-König
2013-03-06 8:47 ` [PATCH v2] mtdchar: handle chips that have user otp but no factory otp Artem Bityutskiy
2013-03-06 8:51 ` Uwe Kleine-König [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=20130306085148.GS22886@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=dedekind1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.