linux-kernel - Re: (subset) [PATCH 0/8] MAINTAINERS and Docs: Use Lee Jones' kernel.org address going forward

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: <165781418870.107719.11036926748201645413.b4-ty@kernel.org>
Date:   Thu, 14 Jul 2022 16:56:28 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lee.jones@...aro.org, lee@...nel.org
Cc:     linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/8] MAINTAINERS and Docs: Use Lee Jones' kernel.org address going forward

On Thu, 14 Jul 2022 12:25:25 +0100, Lee Jones wrote:
> Moving over to my kernel.org address for upstream work.
> 
> Also remove myself from PWM.  Nothing left to do here.
> 
> Lee Jones (8):
>   MAINTAINERS: Use Lee Jones' kernel.org address for MFD submissions
>   MAINTAINERS: Use Lee Jones' kernel.org address for Syscon submissions
>   MAINTAINERS: Remove myself as PWM maintainer
>   docs: ABI: sysfs-class-pwm: Update Lee Jones' email address
>   docs: ABI: sysfs-devices-soc: Update Lee Jones' email address
>   dt-bindings: backlight: Update Lee Jones' email address
>   dt-bindings: mfd: syscon: Update Lee Jones' email address
>   dt-bindings: regulator: pwm: Update Lee Jones' email address
> 
> [...]

Applied to

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

Thanks!

[8/8] dt-bindings: regulator: pwm: Update Lee Jones' email address
      commit: 2f3d2e96b8ea34f21989b75f28d8a6a0e6e6c756

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