From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: "marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
Vineet Gupta <vineet.gupta1@synopsys.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"richard@nod.at" <richard@nod.at>
Subject: Re: [PATCH v2 0/2] MTD: spi-nor: add support for sst26wf016, sst26wf032
Date: Mon, 22 Oct 2018 15:56:35 +0200 [thread overview]
Message-ID: <20181022155635.2175a595@bbrezillon> (raw)
In-Reply-To: <1540216028.19916.6.camel@synopsys.com>
+Tudor
Hi Eugeniy,
On Mon, 22 Oct 2018 13:47:09 +0000
Eugeniy Paltsev <eugeniy.paltsev@synopsys.com> wrote:
> Hi!
>
> Maybe you have any comments or remarks about this patch?And if you don't could you please apply it. Thanks!
Sorry, it's already too late for 4.20, and I won't apply patches to the
spi-nor/next branch before 4.20-rc1 is out.
Tudor, Marek, can I have a Reviewed-by/Acked-by on this patchset?
Thanks,
Boris
>
> On Mon, 2018-09-10 at 14:46 +0300, Eugeniy Paltsev wrote:
> > Add support for the SST sst26wf016 and sst26wf032 flash IC:
> >
> > sst26wf*** flash series block protection implementation differs from other
> > SST series, so we add implementation for sst26wf*** lock/unlock/is_locked
> > functions.
> >
> > Add sst26wf016 and sst26wf032 flash IC info to spi_flash_ids list.
> >
> > NOTE:
> > these patches is basically following mine u-boot commits port:
> > http://git.denx.de/?p=u-boot.git;a=commitdiff;h=3d4fed87a5fa3ffedf64ff2811cd95c5ac4503ac
> > http://git.denx.de/?p=u-boot.git;a=commitdiff;h=a19e97157c3721ef9c4b15c68c1773467a3b4a98
> >
> > Changes v1->v2:
> > * Check return value of {read | write}_reg callbacks.
> >
> > Eugeniy Paltsev (2):
> > mtd: spi-nor: Add support of sst26wf* flash ICs protection ops
> > mtd: spi-nor: add support for sst26wf016, sst26wf032
> >
> > drivers/mtd/spi-nor/spi-nor.c | 179 ++++++++++++++++++++++++++++++++++++++++++
> > include/linux/mtd/spi-nor.h | 4 +
> > 2 files changed, 183 insertions(+)
> >
next prev parent reply other threads:[~2018-10-22 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 11:46 [PATCH v2 0/2] MTD: spi-nor: add support for sst26wf016, sst26wf032 Eugeniy Paltsev
2018-09-10 11:46 ` [PATCH v2 1/2] mtd: spi-nor: Add support of sst26wf* flash ICs protection ops Eugeniy Paltsev
2018-09-24 9:55 ` Eugeniy Paltsev
2018-10-15 14:21 ` Eugeniy Paltsev
2018-11-28 13:17 ` Tudor.Ambarus
2018-10-22 13:46 ` Eugeniy Paltsev
2018-09-10 11:46 ` [PATCH v2 2/2] mtd: spi-nor: add support for sst26wf016, sst26wf032 Eugeniy Paltsev
2018-10-22 13:47 ` [PATCH v2 0/2] MTD: " Eugeniy Paltsev
2018-10-22 13:56 ` Boris Brezillon [this message]
2018-11-19 15:25 ` Eugeniy Paltsev
2018-11-22 17:45 ` Tudor.Ambarus
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=20181022155635.2175a595@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=alexey.brodkin@synopsys.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eugeniy.paltsev@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vineet.gupta1@synopsys.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).