[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZOyPjWooMqAv3IWQ@hovoldconsulting.com>
Date: Mon, 28 Aug 2023 14:14:05 +0200
From: Johan Hovold <johan@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Johan Hovold <johan+linaro@...nel.org>,
Michal Simek <michal.simek@....com>, linux-spi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
Naga Sureshkumar Relli <naga.sureshkumar.relli@...inx.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@...inx.com>
Subject: Re: [PATCH] spi: zynqmp-gqspi: fix clock imbalance on probe failure
Hi Mark,
On Thu, Jun 22, 2023 at 10:42:40PM +0100, Mark Brown wrote:
> On Thu, 22 Jun 2023 10:24:35 +0200, Johan Hovold wrote:
> > Make sure that the device is not runtime suspended before explicitly
> > disabling the clocks on probe failure and on driver unbind to avoid a
> > clock enable-count imbalance.
> >
> >
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/1] spi: zynqmp-gqspi: fix clock imbalance on probe failure
> commit: 1527b076ae2cb6a9c590a02725ed39399fcad1cf
I noticed that this one is still sitting in your for-next (and for-6.4)
branch but that it wasn't included in your 6.6 (or 6.5) pull request.
Did you intend to send it as a fix during the 6.6 cycle or as it fallen
between the cracks somehow?
Johan
Powered by blists - more mailing lists