linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
	John Crispin <john@phrozen.org>,
	Marek Vasut <marek.vasut@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Larry D. Pinney" <ldpinney@gmail.com>
Subject: Re: [PATCH V2 3/3] mtd: spi-nor: add support for ESMT_f25l32qa and ESMT_f25l64qa
Date: Tue, 14 Feb 2017 12:49:42 +0100	[thread overview]
Message-ID: <799e62b0-cbc3-3bae-32ac-9e595992e5d4@gmail.com> (raw)
In-Reply-To: <215ff33d-29a2-e340-9ce9-8c623a11575c@atmel.com>

On 01/30/2017 02:04 PM, Cyrille Pitchen wrote:
> Le 21/12/2016 à 08:23, John Crispin a écrit :
>> From: "Larry D. Pinney" <ldpinney@gmail.com>
>>
>> Add Support for the ESMT_F25L32QA and ESMT_F25L64QA
>> These are 4MB and 8MB SPI NOR Chips from Elite Semiconductor Memory
>> Technology
>>
>> Acked-by: Marek Vasut <marex@denx.de>
>> Signed-off-by: John Crispin <john@phrozen.org>
>> Signed-off-by: Larry D. Pinney <ldpinney@gmail.com>
>> ---
>>  drivers/mtd/spi-nor/spi-nor.c |    2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
>> index bfff159..2b150b5 100644
>> --- a/drivers/mtd/spi-nor/spi-nor.c
>> +++ b/drivers/mtd/spi-nor/spi-nor.c
>> @@ -821,6 +821,8 @@ static int spi_nor_is_locked(struct mtd_info *mtd, loff_t ofs, uint64_t len)
>>
>>  	/* ESMT */
>>  	{ "f25l32pa", INFO(0x8c2016, 0, 64 * 1024, 64, SECT_4K) },
>> +	{ "f25l32qa", INFO(0x8c4116, 0, 64 * 1024, 64, SECT_4K) },
>> +	{ "f25l64qa", INFO(0x8c4117, 0, 64 * 1024, 128, SECT_4K) },
>>
>
> This patch cannot be applied to the github spi-nor tree.
> Another recent patch [1] has updated the "f25l32pa" entry to add the
> SPI_NOR_HAS_LOCK flag. I guess the "f25l{32|64}qa" entries need this flag
> as well.
>
> [1] on the spi-nor tree, commit 252c36bb9c7b ("mtd: spi-nor: Add
> lock/unlock support for f25l32pa")

Hi Larry, I just realized you never resent rebased patch.

Can you do this, please?

      reply	other threads:[~2017-02-14 11:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  7:23 [PATCH V2 0/3] mtd: spi-nor: add some new chip ids John Crispin
2016-12-21  7:23 ` [PATCH V2 1/3] mtd: spi-nor: add support for macronix mx25u25635f John Crispin
2016-12-21  7:32   ` Marek Vasut
2016-12-21 10:41   ` Cyrille Pitchen
2016-12-21  7:23 ` [PATCH V2 2/3] mtd: spi-nor: add support for macronix mx25u3235f John Crispin
2016-12-21  7:33   ` Marek Vasut
2016-12-21  7:36     ` John Crispin
2016-12-21  8:11     ` André Valentin
2016-12-21  8:18       ` John Crispin
2016-12-21 10:07         ` Marek Vasut
2016-12-21 10:13           ` John Crispin
2016-12-21 10:27   ` Cyrille Pitchen
2016-12-21 13:16     ` John Crispin
2016-12-21 13:38       ` Cyrille Pitchen
2016-12-21  7:23 ` [PATCH V2 3/3] mtd: spi-nor: add support for ESMT_f25l32qa and ESMT_f25l64qa John Crispin
2017-01-30 13:04   ` Cyrille Pitchen
2017-02-14 11:49     ` Rafał Miłecki [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=799e62b0-cbc3-3bae-32ac-9e595992e5d4@gmail.com \
    --to=zajec5@gmail.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=john@phrozen.org \
    --cc=ldpinney@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@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;
as well as URLs for NNTP newsgroup(s).