From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stefan Roese <stefan.roese@gmail.com>
Cc: Vikram Narayanan <vikram186@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v3] mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking
Date: Fri, 01 Feb 2013 19:01:47 +0200 [thread overview]
Message-ID: <1359738107.2942.18.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <50F9422D.6020500@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Fri, 2013-01-18 at 13:38 +0100, Stefan Roese wrote:
> >> 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?
Fixed the typo and pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-02-01 17:00 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
2013-02-01 17:01 ` Artem Bityutskiy [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=1359738107.2942.18.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stefan.roese@gmail.com \
--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