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:     quic_plai@quicinc.com, lgirdwood@gmail.com, judyhsiao@chromium.org,
        agross@kernel.org, quic_rohkumar@quicinc.com, bgoswami@quicinc.com,
        quic_srivasam@quicinc.com, bjorn.andersson@linaro.org,
        robh+dt@kernel.org, devicetree@vger.kernel.org,
        srinivas.kandagatla@linaro.org, linux-kernel@vger.kernel.org,
        swboyd@chromium.org, alsa-devel@alsa-project.org,
        linux-arm-msm@vger.kernel.org, perex@perex.cz, tiwai@suse.com
In-Reply-To: <1656326662-14524-1-git-send-email-quic_srivasam@quicinc.com>
References: <1656326662-14524-1-git-send-email-quic_srivasam@quicinc.com>
Subject: Re: [PATCH v2] ASoC: qcom: Add driver support for audioreach solution
Message-Id: <165642585106.1712503.17346348780044575252.b4-ty@kernel.org>
Date:   Tue, 28 Jun 2022 15:17:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 27 Jun 2022 16:14:22 +0530, Srinivasa Rao Mandadapu wrote:
> Add Machine driver support for audioreach solution, which uses
> ADSP in SC7280 based paltforms.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: qcom: Add driver support for audioreach solution
      commit: 5f78e1fb7a3ed1acc355145536ddd54f183b635d

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