linux-kernel - Re: (subset) [PATCH 0/9] Remove pcf50633

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z9CltdJsg_qaTKzQ@gallifrey>
Date: Tue, 11 Mar 2025 21:05:57 +0000
From: "Dr. David Alan Gilbert" <linux@...blig.org>
To: Mark Brown <broonie@...nel.org>
Cc: arnd@...db.de, lee@...nel.org, dmitry.torokhov@...il.com,
	sre@...nel.org, lgirdwood@...il.com, alexandre.belloni@...tlin.com,
	danielt@...nel.org, jingoohan1@...il.com, deller@....de,
	linus.walleij@...aro.org, brgl@...ev.pl, tsbogend@...ha.franken.de,
	linux-mips@...r.kernel.org, linux-input@...r.kernel.org,
	linux-pm@...r.kernel.org, linux-rtc@...r.kernel.org,
	dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/9] Remove pcf50633

* Mark Brown (broonie@...nel.org) wrote:
> On Sun, 09 Mar 2025 19:36:03 +0000, linux@...blig.org wrote:
> > The pcf50633 was used as part of the OpenMoko devices but
> > the support for its main chip was recently removed in:
> > commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
> > 
> > See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
> > 
> > Remove it.
> > 
> > [...]
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> 
> Thanks!
> 
> [6/9] regulator: pcf50633-regulator: Remove
>       commit: 248bc01138b11ff3af38c3b4a39cb8db7aae6eb6

Thanks!
Although....I'd only tested this as part of the series and assumed
someone (Lee?) would pick the lot up in one go.

Dave

> 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
> 
> 
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/