linux-kernel - Re: [PATCH v3] ASoC: atmel-classd: remove codec component

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: <159433200031.57213.7392401769698717985.b4-ty@kernel.org>
Date:   Thu, 09 Jul 2020 23:00:33 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-kernel@...ts.infradead.org,
        Codrin Ciubotariu <codrin.ciubotariu@...rochip.com>,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Cc:     tiwai@...e.com, ludovic.desroches@...rochip.com,
        alexandre.belloni@...tlin.com, lgirdwood@...il.com,
        nicolas.ferre@...rochip.com
Subject: Re: [PATCH v3] ASoC: atmel-classd: remove codec component

On Wed, 8 Jul 2020 13:12:49 +0300, Codrin Ciubotariu wrote:
> The CPU and the codec both are represented now as components, so for
> CLASS-D we are registering two componenets with the same name. Since
> there is no actual codec, we will merge the codec component into the
> CPU one and use a dummy codec instead, for the DAI link.
> As a bonus, debugfs will no longer report an error when will try to
> create entries for both componenets with the same name.

Applied to

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

Thanks!

[1/1] ASoC: atmel-classd: remove codec component
      commit: 1dfdbe73ccf95765135b1b1ee8335ea3cb16bca0

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