linux-kernel - Re: [PATCH] MAINTAINERS: Fix reviewer info for a few ROHM ICs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164942923939.1424555.10954443516187448149.b4-ty@kernel.org>
Date:   Fri, 08 Apr 2022 15:47:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     matti.vaittinen@...rohmeurope.com, mazziesaccount@...il.com
Cc:     linux-kernel@...r.kernel.org, mazziesaccount@...il.com
Subject: Re: [PATCH] MAINTAINERS: Fix reviewer info for a few ROHM ICs

On Fri, 8 Apr 2022 11:32:00 +0300, Matti Vaittinen wrote:
> The email backend used by ROHM keeps labeling patches as spam.
> Additionally, there have been reports of some emails been completely
> dropped. Finally also the email list (or shared inbox)
> linux-power@...rohmeurope.com inadvertly stopped working and has not
> been reviwed during the past few weeks.
> 
> Remove no longer working list 'linux-power' list-entry and switch my
> email to use the personal gmail account instead of the company account.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: Fix reviewer info for a few ROHM ICs
      commit: 908b768f9a8ffca2ef69f3145e23a6a259f99ac3

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