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:     robh+dt@kernel.org, linux-kernel@vger.kernel.org,
        devicetree@vger.kernel.org, tiwai@suse.com, bgoswami@quicinc.com,
        perex@perex.cz, linux-arm-msm@vger.kernel.org, lgirdwood@gmail.com,
        alsa-devel@alsa-project.org, krzysztof.kozlowski+dt@linaro.org
In-Reply-To: <20220916132427.1845-1-srinivas.kandagatla@linaro.org>
References: <20220916132427.1845-1-srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v5 0/5] ASoC: qcom: add support for sc8280xp machine
Message-Id: <166362902680.3419825.7703076569523626210.b4-ty@kernel.org>
Date:   Tue, 20 Sep 2022 00:10:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 16 Sep 2022 14:24:22 +0100, Srinivas Kandagatla wrote:
> This patchset adds support for SC8280XP SoC machine driver.
> 
> First patch moves some of the commonly used code to common from sm8250 machine driver
> and the follow on code adds minimal support for sc8280xp.
> 
> Currently this driver is only tested with SmartSpeakers and Headset
> on Lenovo Thinkpad X13s.
> 
> [...]

Applied to

   broonie/sound.git for-next

Thanks!

[1/5] ASoC: qcom: common: use EXPORT_SYMBOL_GPL instead of EXPORT_SYMBOL
      commit: a25f4e2cdd5d64408b0fa56115ebebd8cc5cb6c0
[2/5] ASoC: dt-bindings: qcom: sort compatible strings
      commit: e4f10cc23cefe16ed69987cb2648f5111e6eacb4
[3/5] ASoC: dt-bindings: qcom,sm8250: add compatibles for sm8450 and sm8250
      commit: f19097cc5adfd29bf2aecd8e0137331fab36946b
[4/5] ASoC: qcom: sm8250: move some code to common
      commit: 3bd975f3ae0a245e4b851c2b0c97b0a71e5359d6
[5/5] ASoC: qcom: add machine driver for sc8280xp
      commit: 295aeea6646ad6cf26c24f5c493ddb60b8f5a0f4

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