linux-kernel - Re: [PATCH RESEND] MAINTAINERS: Remove self from Cirrus Codec drivers

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: <168414898513.394037.16270681416045014663.b4-ty@kernel.org>
Date:   Mon, 15 May 2023 20:09:45 +0900
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com,
        Lucas Tanure <tanureal@...nsource.cirrus.com>
Subject: Re: [PATCH RESEND] MAINTAINERS: Remove self from Cirrus Codec
 drivers

On Fri, 12 May 2023 16:45:03 +0100, Richard Fitzgerald wrote:
> I'm leaving Cirrus Logic, and will no longer have access to
> hardware and documentation necessary to be effective in a
> maintainership role.
> 
> 

Applied to

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

Thanks!

[1/1] MAINTAINERS: Remove self from Cirrus Codec drivers
      commit: dc60b67d259ea63196dcd0400dd43ba062e2e097

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