linux-kernel - Re: [RESEND PATCH] ASoc: tas2781: Rename dai_driver name to unify the name between TAS2563 and TAS2781

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172357230176.112551.2907822029740578323.b4-ty@kernel.org>
Date: Tue, 13 Aug 2024 19:05:01 +0100
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>
Cc: andriy.shevchenko@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz, 
 pierre-louis.bossart@...ux.intel.com, 13916275206@....com, 
 zhourui@...qin.com, alsa-devel@...a-project.org, i-salazar@...com, 
 linux-kernel@...r.kernel.org, j-chadha@...com, liam.r.girdwood@...el.com, 
 jaden-yue@...com, yung-chuan.liao@...ux.intel.com, dipa@...com, 
 yuhsuan@...gle.com, henry.lo@...com, tiwai@...e.de, baojun.xu@...com, 
 soyer@....hu, Baojun.Xu@....com, judyhsiao@...gle.com, navada@...com, 
 cujomalainey@...gle.com, aanya@...com, nayeem.mahmud@...com, 
 savyasanchi.shukla@...radyne.com, flaviopr@...rosoft.com, jesse-ji@...com, 
 darren.ye@...iatek.com, antheas.dk@...il.com, 
 Jerry2.Huang@...uturecenter.com
Subject: Re: [RESEND PATCH] ASoc: tas2781: Rename dai_driver name to unify
 the name between TAS2563 and TAS2781

On Sun, 11 Aug 2024 21:51:41 +0800, Shenghao Ding wrote:
> Rename dai_driver name to unify the name between TAS2563 and
> TAS2781.
> 
> 

Applied to

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

Thanks!

[1/1] ASoc: tas2781: Rename dai_driver name to unify the name between TAS2563 and TAS2781
      commit: 8f712c12f34daaaa2e47ba07cf3b348d3a442986

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