linux-kernel - Re: [PATCH] ASoC: mediatek: mt8173: Fix debugfs registration for components

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: <163675244389.742274.1874559646597511024.b4-ty@kernel.org>
Date:   Fri, 12 Nov 2021 21:27:23 +0000
From:   Mark Brown <broonie@...nel.org>
To:     AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>, lgirdwood@...il.com
Cc:     linux-mediatek@...ts.infradead.org, tiwai@...e.com,
        linux-kernel@...r.kernel.org, pierre-louis.bossart@...ux.intel.com,
        linux-arm-kernel@...ts.infradead.org, alsa-devel@...a-project.org,
        dafna.hirschfeld@...labora.com, perex@...ex.cz,
        matthias.bgg@...il.com, kuninori.morimoto.gx@...esas.com,
        kernel@...labora.com
Subject: Re: [PATCH] ASoC: mediatek: mt8173: Fix debugfs registration for components

On Thu, 11 Nov 2021 17:11:08 +0100, AngeloGioacchino Del Regno wrote:
> When registering the mt8173-afe-pcm driver, we are also adding two
> components: one is for the PCM DAIs and one is for the HDMI DAIs, but
> when debugfs is enabled, we're getting the following issue:
> 
> [   17.279176] debugfs: Directory '11220000.audio-controller' with parent 'mtk-rt5650' already present!
> [   17.288345] debugfs: Directory '11220000.audio-controller' with parent 'mtk-rt5650' already present!
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt8173: Fix debugfs registration for components
      commit: 8c32984bc7da29828260ac514d5d4967f7e8f62d

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