Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     Johan Hovold <johan+linaro@kernel.org>
Cc:     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>
In-Reply-To: <20230622082435.7873-1-johan+linaro@kernel.org>
References: <20230622082435.7873-1-johan+linaro@kernel.org>
Subject: Re: [PATCH] spi: zynqmp-gqspi: fix clock imbalance on probe
 failure
Message-Id: <168747016057.308826.7806530657100324752.b4-ty@kernel.org>
Date:   Thu, 22 Jun 2023 22:42:40 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

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

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark