linux-kernel - Re: [PATCH v9 0/4] ASoc: PCM6240: mixer-test report

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: <171377335622.1755143.2290939269459235170.b4-ty@kernel.org>
Date: Mon, 22 Apr 2024 17:09:16 +0900
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Shenghao Ding <shenghao-ding@...com>
Cc: lgirdwood@...il.com, robh+dt@...nel.org, 
 krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org, 
 linux-sound@...r.kernel.org, devicetree@...r.kernel.org, perex@...ex.cz, 
 tiwai@...e.com, 13916275206@....com, mohit.chawla@...com, soyer@....hu, 
 jkhuang3@...com, tiwai@...e.de, pdjuandi@...com, manisha.agrawal@...com, 
 aviel@...com, hnagalla@...com, praneeth@...com, Baojun.Xu@....com
Subject: Re: [PATCH v9 0/4] ASoc: PCM6240: mixer-test report

On Sun, 07 Apr 2024 17:18:41 +0800, Shenghao Ding wrote:
> v9:
>  - Retest with the code with Volume kcontrol
> v8:
>  - use some reasonable format of changelog.
>  - fixed the format of subject
>  - remove *** BLURB HERE ***
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoc: PCM6240: Create PCM6240 Family driver code
      commit: 1324eafd37aa5c5b970c1b48a857acc81f0685c8
[2/4] ASoc: PCM6240: Create header file for PCM6240 Family driver code
      commit: d537f7b52d71110a98cd7230cce1b56ae7c8ea71
[3/4] ASoc: PCM6240: Add compile item for PCM6240 Family driver
      commit: 6bb1b70690766367e166b8ff59f4b5f9739f7964
[4/4] ASoc: dt-bindings: PCM6240: Add initial DT binding
      commit: cee56a8e9cf89fd690e18eb2e6f09d3f8a6442fb

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