linux-kernel - Re: [PATCH] ASoC: ak5558: Correct the dai name for ak5552

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: <162072058170.33157.387118407952488972.b4-ty@kernel.org>
Date:   Tue, 11 May 2021 09:26:04 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org, Shengjiu Wang <shengjiu.wang@....com>,
        perex@...ex.cz, tiwai@...e.com
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] ASoC: ak5558: Correct the dai name for ak5552

On Sat, 8 May 2021 18:46:47 +0800, Shengjiu Wang wrote:
> Correct the dai name for ak5552. The name should be "ak5552-aif".

Applied to

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

Thanks!

[1/1] ASoC: ak5558: Correct the dai name for ak5552
      commit: b23584d6ce0212b9ad6cb7be19a7123461ed9e09

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