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:     Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc:     perex@perex.cz, tiwai@suse.com, lgirdwood@gmail.com,
        ckeepax@opensource.cirrus.com, kuninori.morimoto.gx@renesas.com,
        linux-kernel@vger.kernel.org, pierre-louis.bossart@linux.intel.com,
        alsa-devel@alsa-project.org
In-Reply-To: <20230509112202.21471-1-srinivas.kandagatla@linaro.org>
References: <20230509112202.21471-1-srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 0/4] ASoC: qcom: add display port module support.
Message-Id: <168378496820.334814.7836507648668066206.b4-ty@kernel.org>
Date:   Thu, 11 May 2023 15:02:48 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 09 May 2023 12:21:58 +0100, Srinivas Kandagatla wrote:
> This patchset adds support to displayport on AudioReach.
> Patches are tested on X13s with two display ports.
> 
> Srinivas Kandagatla (4):
>   ASoC: qcom: q6dsp-common: move channel allocation to common
>   ASoC: qcom: audioreach: add support for DISPLAY PORT SINK module
>   ASoC: qcom: q6dsp: add support to more display ports
>   ASoC: qcom: q6apm: add support to display ports in lpass dais
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: qcom: q6dsp-common: move channel allocation to common
      commit: 4c2be53f411c25b569c8fe3f91d0acfc4c5b8392
[2/4] ASoC: qcom: audioreach: add support for DISPLAY PORT SINK module
      commit: a8ab65417d92803d15cc9aca461ecd9fdb3f2d81
[3/4] ASoC: qcom: q6dsp: add support to more display ports
      commit: 90848a2557fec0a6f1a35e58031a1f6f5e44e7d6
[4/4] ASoC: qcom: q6apm: add support to display ports in lpass dais
      commit: 2f6860e6133fca937d18b66faa32c460cef7ddad

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