linux-kernel - Re: [PATCH v2 0/2] ASoC: codecs: rk3308: fix build warning without OF

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: <171218080011.1232330.13275012484135476972.b4-ty@kernel.org>
Date: Wed, 03 Apr 2024 22:46:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Heiko Stuebner <heiko@...ech.de>, 
 Luca Ceresoli <luca.ceresoli@...tlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v2 0/2] ASoC: codecs: rk3308: fix build warning without
 OF

On Wed, 03 Apr 2024 13:03:17 +0200, Luca Ceresoli wrote:
> This small series fixes a build warning reported by kernel test robot
> <lkp@...el.com> and improves the Kconfig entry.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: codecs: rk3308: fix "defined but not used" warning on !OF
      commit: 38d5387b7660476fd7e8e07d16ee436819e3544d
[2/2] ASoC: codecs: rk3308: depend on ARM64 || COMPILE_TEST
      commit: 03246ade4646653bbc98fa6fa506891a51983259

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