linux-kernel - Re: [PATCH v6 1/4] ASoC: tas2781: Add Header file for tas2781 driver

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: <168721375392.200161.3235917580792681848.b4-ty@kernel.org>
Date:   Mon, 19 Jun 2023 23:29:13 +0100
From:   Mark Brown <broonie@...nel.org>
To:     devicetree@...r.kernel.org, krzysztof.kozlowski+dt@...aro.org,
        robh+dt@...nel.org, lgirdwood@...il.com, perex@...ex.cz,
        pierre-louis.bossart@...ux.intel.com,
        Shenghao Ding <13916275206@....com>
Cc:     kevin-lu@...com, shenghao-ding@...com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, x1077012@...com, peeyush@...com,
        navada@...com, gentuser@...il.com, Ryan_Chu@...tron.com,
        Sam_Wu@...tron.com, tiwai@...e.de
Subject: Re: [PATCH v6 1/4] ASoC: tas2781: Add Header file for tas2781
 driver

On Sun, 18 Jun 2023 20:28:16 +0800, Shenghao Ding wrote:
> Create Header file for  tas2781 driver.
> 
> 

Applied to

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

Thanks!

[1/4] ASoC: tas2781: Add Header file for tas2781 driver
      commit: 678f38eba1f2fe33ff700e85390ac98393e609ef
[2/4] ASoC: tas2781: firmware lib
      commit: 915f5eadebd29ba185ac506766a90120153b7e14
[3/4] ASoC: tas2781: Add tas2781 driver
      commit: ef3bcde75d06d65f78ba38a30d5a87fb83a5cdae
[4/4] ASoC: dt-bindings: Add tas2781 amplifier
      commit: 3e4ecd6c4e14e1eff8f52bd89240399e7dac881c

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