From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Michal Simek <michal.simek@amd.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Subject: Re: [PATCH] spi: zynqmp-gqspi: fix clock imbalance on probe failure
Date: Mon, 28 Aug 2023 14:14:05 +0200 [thread overview]
Message-ID: <ZOyPjWooMqAv3IWQ@hovoldconsulting.com> (raw)
In-Reply-To: <168747016057.308826.7806530657100324752.b4-ty@kernel.org>
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
next prev parent reply other threads:[~2023-08-28 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 8:24 [PATCH] spi: zynqmp-gqspi: fix clock imbalance on probe failure Johan Hovold
2023-06-22 21:42 ` Mark Brown
2023-08-28 12:14 ` Johan Hovold [this message]
2023-08-28 14:52 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZOyPjWooMqAv3IWQ@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=broonie@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=shubhrajyoti.datta@xilinx.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).