From: Marek Vasut <marek.vasut@gmail.com>
To: John Crispin <john@phrozen.org>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
"André Valentin" <avalentin@marcant.net>
Subject: Re: [PATCH 2/2] mtd: spi-nor: add support for mx25u3235f
Date: Wed, 21 Dec 2016 04:38:10 +0100 [thread overview]
Message-ID: <d9c7a7ec-f497-a0ef-8bf4-a75731f1e9c5@gmail.com> (raw)
In-Reply-To: <1482261923-62559-3-git-send-email-john@phrozen.org>
On 12/20/2016 08:25 PM, John Crispin wrote:
> From: André Valentin <avalentin@marcant.net>
>
> Signed-off-by: John Crispin <john@phrozen.org>
> Signed-off-by: André Valentin <avalentin@marcant.net>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 171adb3..f9a41dc 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -868,6 +868,7 @@ static int spi_nor_is_locked(struct mtd_info *mtd, loff_t ofs, uint64_t len)
> { "mx25l3205d", INFO(0xc22016, 0, 64 * 1024, 64, SECT_4K) },
> { "mx25l3255e", INFO(0xc29e16, 0, 64 * 1024, 64, SECT_4K) },
> { "mx25l6405d", INFO(0xc22017, 0, 64 * 1024, 128, SECT_4K) },
> + { "mx25u3235f", INFO(0xc22536, 0, 64 * 1024, 64, 0) },
No SECT_4K support here ?
> { "mx25u6435f", INFO(0xc22537, 0, 64 * 1024, 128, SECT_4K) },
> { "mx25l12805d", INFO(0xc22018, 0, 64 * 1024, 256, 0) },
> { "mx25l12855e", INFO(0xc22618, 0, 64 * 1024, 256, 0) },
>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-12-21 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 19:25 [PATCH 0/2] mtd: spi-nor: add some new chip ids John Crispin
2016-12-20 19:25 ` [PATCH 1/2] mtd: spi-nor: add support for macronix mx25u25635f John Crispin
2016-12-21 3:37 ` Marek Vasut
2016-12-20 19:25 ` [PATCH 2/2] mtd: spi-nor: add support for mx25u3235f John Crispin
2016-12-21 3:38 ` Marek Vasut [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=d9c7a7ec-f497-a0ef-8bf4-a75731f1e9c5@gmail.com \
--to=marek.vasut@gmail.com \
--cc=avalentin@marcant.net \
--cc=cyrille.pitchen@atmel.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).