linux-kernel - Re: [PATCH] ASoC: soc-component: Remove conditional definition of debugfs data members

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: <163313339122.45396.9113357063584478110.b4-ty@kernel.org>
Date:   Sat,  2 Oct 2021 01:16:33 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Simon Trimmer <simont@...nsource.cirrus.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: soc-component: Remove conditional definition of debugfs data members

On Thu, 30 Sep 2021 15:21:16 +0100, Simon Trimmer wrote:
> This simplification allows the use of the standard kernel pattern of
> static inline dummy functions for debugfs code. Most systems will only
> have a small number of snd_soc_components so the memory impact is
> minimal.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: soc-component: Remove conditional definition of debugfs data members
      commit: 0a43c152ed0666dc837009bae031b898ced95e5b

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