From: Brian Norris <computersforpeace@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-mtd@lists.infradead.org,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [PATCH v2] mtd: spi-nor: support GigaDevice gd25lq64c
Date: Fri, 13 May 2016 18:50:22 -0700 [thread overview]
Message-ID: <20160514015022.GC89390@google.com> (raw)
In-Reply-To: <572CC514.1070805@denx.de>
On Fri, May 06, 2016 at 06:23:48PM +0200, Marek Vasut wrote:
> On 05/06/2016 05:37 PM, Brian Norris wrote:
> > Also note the GigaDevice JEDEC ID.
> >
> > No write-protect support yet, since this flash uses a different status
> > register layout.
> >
> > Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> > ---
> > v2: fixed duplicate flag
>
> Acked-by: Marek Vasut <marex@denx.de>
Forgot to note: pushed this to l2-mtd.git several days ago
prev parent reply other threads:[~2016-05-14 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 15:37 [PATCH v2] mtd: spi-nor: support GigaDevice gd25lq64c Brian Norris
2016-05-06 16:23 ` Marek Vasut
2016-05-14 1:50 ` Brian Norris [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=20160514015022.GC89390@google.com \
--to=computersforpeace@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).