linux-kernel - Re: [PATCH] regulator: sm5703: Remove because it is unused and fails to build

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: <172625663174.87505.7759301350549819413.b4-ty@kernel.org>
Date: Fri, 13 Sep 2024 20:43:51 +0100
From: Mark Brown <broonie@...nel.org>
To: markuss.broks@...il.com, Liam Girdwood <lgirdwood@...il.com>, 
 Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] regulator: sm5703: Remove because it is unused and
 fails to build

On Mon, 09 Sep 2024 21:30:51 +0200, Christophe JAILLET wrote:
> This file does not compile because <linux/mfd/sm5703.h> is missing.
> In KConfig, it depends on MFD_SM5703.
> 
> Both MFD_SM5703 and the missing include rely on another patch that never
> got merged. The last iteration related to this patch is [1].
> 
> So remove this dead-code and undo commit e8858ba89ca3 ("regulator:
> sm5703-regulator: Add regulators support for SM5703 MFD")
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: sm5703: Remove because it is unused and fails to build
      commit: 4591a2271f2e4c320eaa63c348169e4e6e6f2852

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