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]
Date: Mon, 05 Feb 2024 16:58:35 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, robh@...nel.org, krzysztof.kozlowski+dt@...aro.org, 
 conor+dt@...nel.org, judyhsiao@...omium.org, quic_bjorande@...cinc.com, 
 Jeffrey Hugo <quic_jhugo@...cinc.com>
Cc: linux-sound@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: google,sc7280-herobrine: Drop
 bouncing @codeaurora

On Fri, 02 Feb 2024 10:43:13 -0700, Jeffrey Hugo wrote:
> The servers for the @codeaurora domain have long been retired and any
> messages sent there bounce.  Srinivasa Rao Mandadapu has left the
> company and there does not appear to be an updated address to suggest,
> so drop Srinivasa as maintainer of the binding.  The binding still
> appears to be maintined as Judy is listed.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: google,sc7280-herobrine: Drop bouncing @codeaurora
      commit: ac670505d825151ce47c1e75b9964485991954dd

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ