Received-SPF: pass (google.com: domain of linux-kernel+bounces-131717-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Mark Brown <broonie@kernel.org>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
Cc: lgirdwood@gmail.com, peter.ujfalusi@linux.intel.com, 
 pierre-louis.bossart@linux.intel.com, daniel.baluta@nxp.com, 
 iuliana.prodan@nxp.com, linux-sound@vger.kernel.org, imx@lists.linux.dev, 
 laurentiu.mihalcea@nxp.com, linux-kernel@vger.kernel.org
In-Reply-To: <20240328221201.24722-1-laurentiumihalcea111@gmail.com>
References: <20240328221201.24722-1-laurentiumihalcea111@gmail.com>
Subject: Re: [PATCH 0/2] ASoC: SOF: imx: stop using the imx8_*_clocks API
Message-Id: <171224425330.53181.2036893108505184171.b4-ty@kernel.org>
Date: Thu, 04 Apr 2024 16:24:13 +0100
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Fri, 29 Mar 2024 00:11:59 +0200, Laurentiu Mihalcea wrote:
> The imx8_*_clocks API requires keeping track of all of the clocks used
> by the IMX SOF driver via an array. This is unnecessary and doesn't
> scale well. As such, remove it altogether and replace it with
> devm_clk_bulk_get_all() and friends.
> 
> Laurentiu Mihalcea (2):
>   ASoC: SOF: imx: drop usage of the imx8_*_clocks API
>   ASoC: SOF: imx: remove imx8_*_clocks API
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: SOF: imx: drop usage of the imx8_*_clocks API
      commit: a358f67d16942f3bbc4d6b0e4b65efd5dda1c304
[2/2] ASoC: SOF: imx: remove imx8_*_clocks API
      commit: e618b8b37aa1dac42f50c87373d71ecc68ead97d

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