linux-kernel - Re: [PATCH v1 0/2] ASoC: qcom: add support for QRB5165 RB5 machine

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <160375592348.31132.700517684060539910.b4-ty@kernel.org>
Date:   Mon, 26 Oct 2020 23:46:22 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     spapothi@...eaurora.org, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        plai@...eaurora.org
Subject: Re: [PATCH v1 0/2] ASoC: qcom: add support for QRB5165 RB5 machine

On Mon, 26 Oct 2020 17:09:45 +0000, Srinivas Kandagatla wrote:
> This patchset adds support to Qualcomm Robotics RB5 Development Kit based on
> QRB5165 Robotics SoC. This board has 2 WSA881X smart speakers with onboard
> DMIC connected to internal LPASS codec via WSA and VA macros respectively.
> 
> Srinivas Kandagatla (2):
>   ASoC: qcom: dt-bindings: Add SM8250 sound card bindings
>   ASoC: qcom: sm8250: add sound card qrb5165-rb5 support
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: qcom: dt-bindings: Add SM8250 sound card bindings
      commit: 765c37598494cdb6c8f833e8e46f494af5c7d39e
[2/2] ASoC: qcom: sm8250: add sound card qrb5165-rb5 support
      commit: aa2e2785545aab21b6cb2e23f111ae0751cbcca7

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