[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0007c019-1ecf-1913-56a7-facffe345b1f@microchip.com>
Date: Fri, 19 Jun 2020 11:47:08 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <broonie@...nel.org>, <vigneshr@...com>
CC: <bbrezillon@...nel.org>,
<vadivel.muruganx.ramuthevar@...ux.intel.com>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-spi@...r.kernel.org>, <simon.k.r.goldschmidt@...il.com>,
<dinguyen@...nel.org>, <marex@...x.de>
Subject: Re: [RESEND PATCH v3 0/8] mtd: spi-nor: Move cadence-qaudspi to
spi-mem framework
On 6/19/20 1:57 PM, Mark Brown wrote:
>> This series is a subset of "[PATCH v12 0/4] spi: cadence-quadspi: Add
>> support for the Cadence QSPI controller" by Ramuthevar,Vadivel MuruganX
>> <vadivel.muruganx.ramuthevar@...ux.intel.com> that intended to move
>> cadence-quadspi driver to spi-mem framework
> Are people OK with me applying this to the SPI tree?
There's a small conflict on 8/8 when applying on top of v5.8-rc1. With
that addressed:
Acked-by: Tudor Ambarus <tudor.ambarus@...rochip.com>
Would you please provide an immutable tag on top of v5.8-rc1 so that I
can merge back in spi-nor/next?
Cheers,
ta
Powered by blists - more mailing lists