From: <Tudor.Ambarus@microchip.com>
To: <vigneshr@ti.com>, <broonie@kernel.org>
Cc: <bbrezillon@kernel.org>,
<vadivel.muruganx.ramuthevar@linux.intel.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <simon.k.r.goldschmidt@gmail.com>,
<dinguyen@kernel.org>, <marex@denx.de>
Subject: Re: [PATCH v3 8/8] spi: Move cadence-quadspi driver to drivers/spi/
Date: Mon, 1 Jun 2020 07:00:34 +0000 [thread overview]
Message-ID: <2051214.IORyQiarUF@192.168.0.120> (raw)
In-Reply-To: <20200601054725.2060-9-vigneshr@ti.com>
Hi, Mark,
On Monday, June 1, 2020 8:47:25 AM EEST Vignesh Raghavendra wrote:
> From: Ramuthevar Vadivel Murugan
> <vadivel.muruganx.ramuthevar@linux.intel.com>
>
> Now that cadence-quadspi has been converted to use spi-mem framework,
> move it under drivers/spi/
>
> Update license header to match SPI subsystem style
>
> Signed-off-by: Ramuthevar Vadivel Murugan
> <vadivel.muruganx.ramuthevar@linux.intel.com> Signed-off-by: Vignesh
> Raghavendra <vigneshr@ti.com>
> ---
> drivers/mtd/spi-nor/controllers/Kconfig | 11 -----------
> drivers/mtd/spi-nor/controllers/Makefile | 1 -
> drivers/spi/Kconfig | 11 +++++++++++
> drivers/spi/Makefile | 1 +
> .../spi-cadence-quadspi.c} | 14 +++++++-------
> 5 files changed, 19 insertions(+), 19 deletions(-)
> rename drivers/{mtd/spi-nor/controllers/cadence-quadspi.c =>
> spi/spi-cadence-quadspi.c} (99%)
If this patch set looks good to you, would you take it through the SPI tree?
If so, I would need an immutable tag, so I can merge back in spi-nor/next in
order to fix a small conflict that will appear in drivers/mtd/spi-nor/
controllers/Kconfig. Vignesh would have to respin this patch on top of v5.7-
rc1. With this addressed:
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
next prev parent reply other threads:[~2020-06-01 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 5:47 [PATCH v3 0/8] mtd: spi-nor: Move cadence-qaudspi to spi-mem framework Vignesh Raghavendra
2020-06-01 5:47 ` [PATCH v3 1/8] mtd: spi-nor: cadence-quadspi: Make driver independent of flash geometry Vignesh Raghavendra
2020-06-01 5:47 ` [PATCH v3 2/8] mtd: spi-nor: cadence-quadspi: Provide a way to disable DAC mode Vignesh Raghavendra
2020-06-01 5:47 ` [PATCH v3 3/8] mtd: spi-nor: cadence-quadspi: Don't initialize rx_dma_complete on failure Vignesh Raghavendra
2020-06-01 5:47 ` [PATCH v3 4/8] mtd: spi-nor: cadence-quadspi: Fix error path on failure to acquire reset lines Vignesh Raghavendra
2020-06-01 5:47 ` [PATCH v3 5/8] mtd: spi-nor: cadence-quadspi: Handle probe deferral while requesting DMA channel Vignesh Raghavendra
2020-06-01 6:31 ` Tudor.Ambarus
2020-06-01 5:47 ` [PATCH v3 6/8] mtd: spi-nor: cadence-quadspi: Drop redundant WREN in erase path Vignesh Raghavendra
2020-06-01 6:32 ` Tudor.Ambarus
2020-06-01 5:47 ` [PATCH v3 7/8] mtd: spi-nor: Convert cadence-quadspi to use spi-mem framework Vignesh Raghavendra
2020-06-01 6:49 ` Tudor.Ambarus
2020-06-01 5:47 ` [PATCH v3 8/8] spi: Move cadence-quadspi driver to drivers/spi/ Vignesh Raghavendra
2020-06-01 7:00 ` Tudor.Ambarus [this message]
2020-06-01 7:07 ` Vignesh Raghavendra
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=2051214.IORyQiarUF@192.168.0.120 \
--to=tudor.ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=vigneshr@ti.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).