From: John Crispin <john@phrozen.org>
To: "Marek Vasut" <marek.vasut@gmail.com>,
"André Valentin" <avalentin@marcant.net>,
"Cyrille Pitchen" <cyrille.pitchen@atmel.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/3] mtd: spi-nor: add support for macronix mx25u3235f
Date: Wed, 21 Dec 2016 11:13:42 +0100 [thread overview]
Message-ID: <6672a471-fad3-3ed3-528d-e4f92492f4dc@phrozen.org> (raw)
In-Reply-To: <2a6961e5-51ac-e6ac-ff8f-a1147d61808d@gmail.com>
On 21/12/2016 11:07, Marek Vasut wrote:
> On 12/21/2016 09:18 AM, John Crispin wrote:
>> Hi André
>>
>> could you test if it also works when enabling SECT_4K please ?
>
> Yes, please test, thanks.
>
> btw please do stop top-posting.
>
>> John
>>
Sorry about top posting. André will need a bit of time to test so i will
send a V3 with only the other 2 patches included today and then send
this patch later once tested.
John
next prev parent reply other threads:[~2016-12-21 10:13 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 [this message]
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
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=6672a471-fad3-3ed3-528d-e4f92492f4dc@phrozen.org \
--to=john@phrozen.org \
--cc=avalentin@marcant.net \
--cc=cyrille.pitchen@atmel.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).