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

Luca Ceresoli posted 2 patches 1 year, 10 months ago
sound/soc/codecs/Kconfig        | 1 +
sound/soc/codecs/rk3308_codec.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
[PATCH v2 0/2] ASoC: codecs: rk3308: fix build warning without OF
Posted by Luca Ceresoli 1 year, 10 months ago
This small series fixes a build warning reported by kernel test robot
<lkp@intel.com> and improves the Kconfig entry.

Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
---
Changes in v2:
- Replaced v1 implementation with __maybe_unused
- Added patch to depend on || COMPILE_TEST
- Link to v1: https://lore.kernel.org/r/20240329-rk3308-audio-codec-fix-warning-v1-1-b9d177fcd6c9@bootlin.com

---
Luca Ceresoli (2):
      ASoC: codecs: rk3308: fix "defined but not used" warning on !OF
      ASoC: codecs: rk3308: depend on ARM64 || COMPILE_TEST

 sound/soc/codecs/Kconfig        | 1 +
 sound/soc/codecs/rk3308_codec.c | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)
---
base-commit: 4ed0915f5bc4bcc81bca783a5b984f3d81e9764e
change-id: 20240329-rk3308-audio-codec-fix-warning-51bb572ebd96

Best regards,
-- 
Luca Ceresoli <luca.ceresoli@bootlin.com>
Re: [PATCH v2 0/2] ASoC: codecs: rk3308: fix build warning without OF
Posted by Mark Brown 1 year, 10 months ago
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@intel.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