From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <bbrezillon@kernel.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org, Stefan Roese <sr@denx.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v5] mtd: spinand: Use the spi-mem dirmap API
Date: Mon, 1 Apr 2019 17:22:03 +0200 [thread overview]
Message-ID: <20190401172203.61ae76c4@xps13> (raw)
In-Reply-To: <20190124145643.3195-1-bbrezillon@kernel.org>
Hi Boris,
Boris Brezillon <bbrezillon@kernel.org> wrote on Thu, 24 Jan 2019
15:56:43 +0100:
> Make use of the spi-mem direct mapping API to let advanced controllers
> optimize read/write operations when they support direct mapping.
>
> Signed-off-by: Boris Brezillon <bbrezillon@kernel.org>
> Cc: Stefan Roese <sr@denx.de>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> Note that this patch now depends on [1] and [2] and should not be
> queued for 5.1 but for 5.2.
>
> [1]https://patchwork.kernel.org/patch/10772067/
> [2]http://patchwork.ozlabs.org/patch/1030479/
>
> Changes in v5:
> - Update my email address in the SoB and Author fields
>
> Changes in v4:
> - Fix various bugs reported by Stefan
> - Use devm_spi_mem_dirmap_create() to simplify the error/remove path
> - Drop Miquel's R-b as a few important things have changed in this v4
>
> Changes in v3:
> - Add Miquel's R-b
>
> Changes in v2:
> - New patch
> ---
Applied to git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
on nand/next.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-04-01 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 14:56 [PATCH v5] mtd: spinand: Use the spi-mem dirmap API Boris Brezillon
2019-01-24 15:21 ` Stefan Roese
2019-01-25 13:11 ` Miquel Raynal
2019-04-01 15:22 ` 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=20190401172203.61ae76c4@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=sr@denx.de \
/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.