From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH 0/2] mtd: rawnand: Make ->dev_ready() and ->chip_delay optional
Date: Tue, 4 Sep 2018 23:47:27 +0200 [thread overview]
Message-ID: <20180904234727.39f1d249@xps13> (raw)
In-Reply-To: <20180727074418.32384-1-boris.brezillon@bootlin.com>
Hi Boris,
Boris Brezillon <boris.brezillon@bootlin.com> wrote on Fri, 27 Jul 2018
09:44:16 +0200:
> Hello,
>
> These 2 patches remove the last dependency we had on ->dev_ready() and
> ->chip_delay when ->exec_op() is defined. Will be needed to deprecate
> both fields, which is about to happen (see this branch [1] if you want
> to have the big picture).
>
> Regards,
>
> Boris
>
> [1]https://github.com/bbrezillon/linux-0day/commits/nand/api-cleanup
>
> Boris Brezillon (2):
> mtd: rawnand: Add the nand_wait_readrdy() helper and use it
> mtd: rawnand: Add the nand_wait_rdy_op() helper and use it
>
> drivers/mtd/nand/raw/nand_base.c | 49 ++++++++++++++++++++++++++++------------
> 1 file changed, 35 insertions(+), 14 deletions(-)
>
Applied to nand/next.
Thanks
--
Miquel Raynal, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-04 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 7:44 [PATCH 0/2] mtd: rawnand: Make ->dev_ready() and ->chip_delay optional Boris Brezillon
2018-07-27 7:44 ` [PATCH 1/2] mtd: rawnand: Add the nand_wait_readrdy() helper and use it Boris Brezillon
2018-07-27 7:44 ` [PATCH 2/2] mtd: rawnand: Add the nand_wait_rdy_op() " Boris Brezillon
2018-09-04 21:47 ` 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=20180904234727.39f1d249@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.