linux-kernel - Re: [PATCH] ASoC: mediatek: btcvsd fix tx stream assign

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 for Android: free password hash cracker in your pocket

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

Message-Id: <160675530955.30326.8266521477804403197.b4-ty@kernel.org>
Date:   Mon, 30 Nov 2020 16:55:31 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Lumi Lee <Lumi.Lee@...iatek.com>,
        Matthias Brugger <matthias.bgg@...il.com>
Cc:     Lumi Lee <lumi.lee@...iatek.com>, linux-kernel@...r.kernel.org,
        Shane.Chien@...iatek.com, eason.yen@...iatek.com,
        devicetree@...r.kernel.org, wsd_upstream@...iatek.com,
        linux-mediatek@...ts.infradead.org, jiaxin.yu@...iatek.com,
        alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: mediatek: btcvsd fix tx stream assign

On Mon, 30 Nov 2020 11:11:15 +0800, Lumi Lee wrote:
> Fix tx/rx stream assign in write.
> Write should use tx instead of rx.

Applied to

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

Thanks!

[1/1] ASoC: mediatek: btcvsd fix tx stream assign
      commit: bbe1f69dce94089943cc407a88325ae7e851d49c

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