[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190115151818.GD13895@dragon>
Date: Tue, 15 Jan 2019 23:18:19 +0800
From: Shawn Guo <shawnguo@...nel.org>
To: Schrempf Frieder <frieder.schrempf@...tron.de>
Cc: "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"boris.brezillon@...tlin.com" <boris.brezillon@...tlin.com>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"broonie@...nel.org" <broonie@...nel.org>,
Li Yang <leoyang.li@....com>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"computersforpeace@...il.com" <computersforpeace@...il.com>,
"marek.vasut@...il.com" <marek.vasut@...il.com>,
"richard@....at" <richard@....at>,
"miquel.raynal@...tlin.com" <miquel.raynal@...tlin.com>,
"david.wolfe@....com" <david.wolfe@....com>,
"fabio.estevam@....com" <fabio.estevam@....com>,
"prabhakar.kushwaha@....com" <prabhakar.kushwaha@....com>,
"yogeshnarayan.gaur@....com" <yogeshnarayan.gaur@....com>,
"han.xu@....com" <han.xu@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 5/7] ARM: dts: ls1021a: Remove
fsl,qspi-has-second-chip as it is not used
On Mon, Jan 14, 2019 at 08:18:49AM +0000, Schrempf Frieder wrote:
> Hi Shawn,
>
> On 13.01.19 04:31, Shawn Guo wrote:
> > On Mon, Jan 07, 2019 at 09:29:54AM +0000, Schrempf Frieder wrote:
> >> From: Frieder Schrempf <frieder.schrempf@...tron.de>
> >>
> >> After switching to the new FSL QSPI driver the property
> >> 'fsl,qspi-has-second-chip' is not needed anymore.
> >>
> >> The driver now uses the 'reg' property to determine the bus and
> >> the chipselect.
> >>
> >> Signed-off-by: Frieder Schrempf <frieder.schrempf@...tron.de>
> >
> > Applied, thanks.
>
> I just noticed, that this and the arm64 patch depend on the driver
> changes for 5.1 that go through the SPI tree. So I guess we can't be
> sure that this will be merged in the right order and we need to delay
> this cleanup to 5.2, or am I wrong?
You are right. I just dropped the both patches. Ping me or resend when
they are ready to go.
Shawn
Powered by blists - more mailing lists