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: <173980274756.49890.13014040253628029521.b4-ty@kernel.org>
Date: Mon, 17 Feb 2025 14:32:27 +0000
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>, Kevin Lu <kevin-lu@...com>, 
 Baojun Xu <baojun.xu@...com>, Liam Girdwood <lgirdwood@...il.com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Dan Murphy <dmurphy@...com>, Hector Martin <marcan@...can.st>, 
 Martin PoviĊĦer <povik+lin@...ebit.org>, broonie@...nel.org
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH 0/4] ASoC: tas2764: Random patches from the Asahi Linux
 tree

On Sat, 08 Feb 2025 01:03:23 +0000, broonie@...nel.org wrote:
> This is a random subset of the patches for the tas2764 driver that I
> found in the Asahi Linux tree which seemed to be clear fixes and
> improvements which apply easily to mainline without much effort, there's
> a bunch more work on the driver that should also be applicable.
> 
> I've only build tested this.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: tas2764: Power up/down amp on mute ops
      commit: 1c3b5f37409682184669457a5bdf761268eafbe5
[2/4] ASoC: tas2764: Wait for ramp-down after shutdown
      commit: 08a66f55f7246d477b19620a953476dfc02beefc
[3/4] ASoC: tas2764: Mark SW_RESET as volatile
      commit: f37f1748564ac51d32f7588bd7bfc99913ccab8e
[4/4] ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG
      commit: d64c4c3d1c578f98d70db1c5e2535b47adce9d07

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