[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200624180005.GO5472@sirena.org.uk>
Date: Wed, 24 Jun 2020 19:00:05 +0100
From: Mark Brown <broonie@...nel.org>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Rajendra Nayak <rnayak@...eaurora.org>, bjorn.andersson@...aro.org,
agross@...nel.org, robdclark@...il.com, robdclark@...omium.org,
stanimir.varbanov@...aro.org, viresh.kumar@...aro.org,
sboyd@...nel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, Alok Chauhan <alokc@...eaurora.org>,
Akash Asthana <akashast@...eaurora.org>,
linux-spi@...r.kernel.org
Subject: Re: [PATCH v6 6/6] spi: spi-qcom-qspi: Use OPP API to set clk/perf
state
On Wed, Jun 24, 2020 at 10:55:36AM -0700, Matthias Kaehlcke wrote:
> On Wed, Jun 24, 2020 at 06:44:17PM +0100, Mark Brown wrote:
> > Wait, so *some* of the series should go together but not other bits?
> > But you want them split up for some reason?
> Yes, this will almost certainly be the case, even if not for this patch.
> I brought this up earlier (https://patchwork.kernel.org/cover/11604623/#23428709).
I'm not really reading any of this stuff for the series as a whole, as
far as I could tell I'd reviewed all my bits and was hoping whatever
random platform stuff needs sorting out was going to be sorted out so I
stopped getting copied on revisions :(
> For the QSPI patch you could argue to just take it through QCOM since the SPI
> patch of this series goes through this tree, up to you, I just want to make
> sure everybody is on the same page.
If there are some part of this that don't have a connection with the
rest of the series and should be applied separately please split them
out and send them separately so it's clear what's going on.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists