From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Wenyou Yang <wenyou.yang@microchip.com>,
Jagdish Gediya <jagdish.gediya@nxp.com>,
Jane Wan <Jane.Wan@nokia.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mtd: rawnand: fsl_ifc: fix SRAM initialization for newer controller
Date: Tue, 4 Sep 2018 23:55:35 +0200 [thread overview]
Message-ID: <20180904235535.165be621@xps13> (raw)
In-Reply-To: <20180813071846.9433-1-kurt@linutronix.de>
Hi Kurt,
Kurt Kanzenbach <kurt@linutronix.de> wrote on Mon, 13 Aug 2018 09:18:44
+0200:
> Hi,
>
> this is version two of
>
> lkml.kernel.org/r/20180806092137.9287-1-kurt@linutronix.de
>
> Changes since v1:
>
> - Addressed comments from Miquel Raynal
> - Changed subject
> - Coding style
> - Using timeout constants
> - Moving version check completely into fsl_ifc_sram_init()
>
> Thanks,
> Kurt
>
> Kurt Kanzenbach (2):
> mtd: rawnand: fsl_ifc: check result of SRAM initialization
> mtd: rawnand: fsl_ifc: fixup SRAM init for newer ctrl versions
>
> drivers/mtd/nand/raw/fsl_ifc_nand.c | 36 ++++++++++++++++++++++++++++++++----
> include/linux/fsl_ifc.h | 2 ++
> 2 files changed, 34 insertions(+), 4 deletions(-)
>
Series applied to nand/next.
Thanks,
Miquèl
prev parent reply other threads:[~2018-09-04 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 7:18 [PATCH v2 0/2] mtd: rawnand: fsl_ifc: fix SRAM initialization for newer controller Kurt Kanzenbach
2018-08-13 7:18 ` [PATCH v2 1/2] mtd: rawnand: fsl_ifc: check result of SRAM initialization Kurt Kanzenbach
2018-08-13 7:18 ` [PATCH v2 2/2] mtd: rawnand: fsl_ifc: fixup SRAM init for newer ctrl versions Kurt Kanzenbach
2018-09-04 21:55 ` Miquel Raynal [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=20180904235535.165be621@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Jane.Wan@nokia.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jagdish.gediya@nxp.com \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=wenyou.yang@microchip.com \
--cc=yamada.masahiro@socionext.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).