Received-SPF: pass (google.com: domain of linux-kernel+bounces-169024-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>, Jaroslav Kysela <perex@perex.cz>, 
 Takashi Iwai <tiwai@suse.com>, linux-sound@vger.kernel.org, 
 linux-kernel@vger.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
In-Reply-To: <20240501175127.34301-1-krzysztof.kozlowski@linaro.org>
References: <20240501175127.34301-1-krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2] ASoC: Use inline function for type safety in
 snd_soc_substream_to_rtd()
Message-Id: <171492138663.1933443.10503961369232756319.b4-ty@kernel.org>
Date: Mon, 06 May 2024 00:03:06 +0900
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Wed, 01 May 2024 19:51:27 +0200, Krzysztof Kozlowski wrote:
> A common pattern in sound drivers is getting 'struct snd_soc_pcm_runtime'
> from 'struct snd_pcm_substream' opaque pointer private_data field with
> snd_soc_substream_to_rtd().  However 'private_data' appears in several
> other structures as well, including 'struct snd_compr_stream'.  The
> field might not hold the same type for every structure, although seems
> the case at least for 'struct snd_compr_stream', so code can easily make
> a mistake by using macro for wrong structure passed as argument.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Use inline function for type safety in snd_soc_substream_to_rtd()
      commit: 9723cab054d59d770cd1927f92fe315c26cc6a78

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