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  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]
Date:   Wed, 16 Dec 2020 15:52:57 +0000
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, Peter Ujfalusi <peter.ujfalusi@...com>,
        lgirdwood@...il.com, jarkko.nikula@...mer.com
Cc:     devicetree@...r.kernel.org, linux-omap@...r.kernel.org,
        linux-kernel@...r.kernel.org, tiwai@...e.com,
        alsa-devel@...a-project.org, linux-arm-kernel@...ts.infradead.org,
        jsarha@...com
Subject: Re: [PATCH 0/2] ASoC: ti: Maintainer mail address change

On Tue, 15 Dec 2020 15:05:10 +0200, Peter Ujfalusi wrote:
> My TI address is going to bounce after Friday (18.12.2020), switch my email
> address to my private one for now.
> 
> Regards,
> Peter

Applied to

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

Thanks!

[1/2] MAINTAINERS: Update email address for TI ASoC and twl4030 codec drivers
      commit: fe6ce6c394fb1ef1d8a6384c5180e70893157f22
[2/2] ASoC: dt-bindings: ti, j721e: Update maintainer and author information
      commit: 61fc03b6512b18f27a25002426d595f5a36645ed

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

Powered by blists - more mailing lists