linux-kernel - Re: [PATCH -next] ASoC: samsung: fix platform_no_drv

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: <160573314460.46437.7362615607650811363.b4-ty@kernel.org>
Date:   Wed, 18 Nov 2020 20:59:21 +0000
From:   Mark Brown <broonie@...nel.org>
To:     s.nawrocki@...sung.com, perex@...ex.cz, tiwai@...e.com,
        krzk@...nel.org, Zou Wei <zou_wei@...wei.com>, lgirdwood@...il.com
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH -next] ASoC: samsung: fix platform_no_drv_owner.cocci warnings

On Mon, 16 Nov 2020 20:29:00 +0800, Zou Wei wrote:
> ./sound/soc/samsung/midas_wm1811.c:534:3-8: No need to set .owner here. The core will do it.
> 
>  Remove .owner field if calls are used which set it automatically
> 
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci

Applied to

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

Thanks!

[1/1] ASoC: samsung: fix platform_no_drv_owner.cocci warnings
      commit: 45f366ec7941932d1a14576f3bd73d831fe9da95

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