linux-kernel - Re: [PATCH 1/2] ASoc: q6afe: add support to get port direction

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] [day] [month] [year] [list]

Message-Id: <159223353044.8967.4267093488191293280.b4-ty@kernel.org>
Date:   Mon, 15 Jun 2020 16:05:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     linux-kernel@...r.kernel.org, John Stultz <john.stultz@...aro.org>,
        vkoul@...nel.org, lgirdwood@...il.com, tiwai@...e.com,
        alsa-devel@...a-project.org
Subject: Re: [PATCH 1/2] ASoc: q6afe: add support to get port direction

On Fri, 12 Jun 2020 13:37:10 +0100, Srinivas Kandagatla wrote:
> This patch adds support to q6afe_is_rx_port() to get direction
> of DSP BE dai port, this is useful for setting dailink
> directions correctly.

Applied to

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

Thanks!

[1/2] ASoc: q6afe: add support to get port direction
      commit: 4a95737440d426e93441d49d11abf4c6526d4666
[2/2] ASoC: qcom: common: set correct directions for dailinks
      commit: a2120089251f1fe221305e88df99af16f940e236

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