From: Stefan Roese <stefan.roese@gmail.com>
To: Vikram Narayanan <vikram186@gmail.com>
Cc: linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH v3] mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking
Date: Fri, 18 Jan 2013 13:38:05 +0100 [thread overview]
Message-ID: <50F9422D.6020500@gmail.com> (raw)
In-Reply-To: <50F94122.3000609@gmail.com>
On 01/18/2013 01:33 PM, Vikram Narayanan wrote:
> On 1/18/2013 5:40 PM, Stefan Roese wrote:
> <snip>
>> nor_flash@0,0 {
>> compatible = "amd,s29gl256n", "cfi-flash";
>> bank-width = <2>;
>> use-advanced-sector-protection;
>> ...
>>
>> Tested with Spanion S29GL512S10THI and Micron JS28F512M29EWx flash
>> devices.
>
> Minor nitpick.
> Isn't it Spansion?
Yes, of course. Artem, should I send a new patch version for this
spelling error?
Thanks,
Stefan
next prev parent reply other threads:[~2013-01-18 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 12:10 [PATCH v3] mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking Stefan Roese
2013-01-18 12:33 ` Vikram Narayanan
2013-01-18 12:38 ` Stefan Roese [this message]
2013-02-01 17:01 ` Artem Bityutskiy
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=50F9422D.6020500@gmail.com \
--to=stefan.roese@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vikram186@gmail.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