linux-kernel - Re: (subset) [PATCH 1/3] MAINTAINERS: add myself for spi-bcm63xx

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: <168848534358.86644.6954201495019514994.b4-ty@kernel.org>
Date:   Tue, 04 Jul 2023 16:42:23 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jonas Gorski <jonas.gorski@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 1/3] MAINTAINERS: add myself for spi-bcm63xx

On Fri, 30 Jun 2023 22:22:54 +0200, Jonas Gorski wrote:
> I noticed the driver is unclaimed. Since I was the last one doing
> substantial work on it, add me as the maintainer.
> 
> As it is only found in legacy products, mark it as "Odd Fixes"
> instead of "Maintained".
> 
> 
> [...]

Applied to

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

Thanks!

[2/3] spi: bcm{63xx,bca}-hsspi: update my email address
      commit: 879a879c216a41f5403d8d3dbc204a48501912bf

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