[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180802134804.2352ee89@bbrezillon>
Date: Thu, 2 Aug 2018 13:48:04 +0200
From: Boris Brezillon <boris.brezillon@...tlin.com>
To: Frieder Schrempf <frieder.schrempf@...eet.de>
Cc: Mark Brown <broonie@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Richard Weinberger <richard@....at>,
Piotr Bugalski <pbu@...ptera.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
Marek Vasut <marek.vasut@...il.com>,
Rob Herring <robh+dt@...nel.org>,
linux-mtd@...ts.infradead.org,
Piotr Bugalski <bugalski.piotr@...il.com>,
Brian Norris <computersforpeace@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
linux-arm-kernel@...ts.infradead.org,
Cyrille Pitchen <cyrille.pitchen@...rochip.com>
Subject: Re: [RFC PATCH v2 5/6] spi: Add QuadSPI driver for Atmel SAMA5D2
On Thu, 2 Aug 2018 12:46:36 +0200
Frieder Schrempf <frieder.schrempf@...eet.de> wrote:
> Hi Mark,
>
> On 02.08.2018 12:17, Mark Brown wrote:
> > On Wed, Aug 01, 2018 at 09:57:33PM +0200, Boris Brezillon wrote:
> >> Mark Brown <broonie@...nel.org> wrote:
> >
> >> 2/ Getting this patch [1] merged and implementing the ->get_name() hook
> >> in this driver so that SPI NOR devs declared to the MTD layer keep
> >> the same name after the transition to spi-mem and mtdparts= passed on
> >> the cmdline keep working. Without this in place we're likely to
> >> break a few setups :-/.
> >
> >> [1]https://patchwork.kernel.org/patch/10508693/
> >
> > I don't seem to have a copy of this patch... not sure it was sent to
> > me?
>
> When I sent the patch I put you in cc. So if nothing went wrong you
> should have it.
> It is part of the SPI MEM conversion series for the FSL QSPI driver [1].
>
> Boris made some remarks on documentation in v2, that I have fixed, but
> not sent out yet, as we have some blocking issues with the driver itself.
I don't remember where we were stuck. Are you still waiting answers
from Yogesh? Probably a good time to ping him if that's the case ;-).
>
> So if you want I could send the patch separately so it can be applied
> with the Atmel driver.
Yes please, send a v3 for patch 1 and 2.
Powered by blists - more mailing lists