[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161910991989.37460.309965109490904776.b4-ty@kernel.org>
Date: Thu, 22 Apr 2021 17:48:48 +0100
From: Mark Brown <broonie@...nel.org>
To: Dmitry Osipenko <digetx@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Arnd Bergmann <arnd@...nel.org>
Cc: Mark Brown <broonie@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Takashi Iwai <tiwai@...e.com>, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org, Qiushi Wu <wu000273@....edu>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Arnd Bergmann <arnd@...db.de>, alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: tegra: mark runtime-pm functions as __maybe_unused
On Thu, 22 Apr 2021 15:34:00 +0200, Arnd Bergmann wrote:
> A reorganization of the driver source led to two of them causing
> a compile time warning in some configurations:
>
> tegra/tegra20_spdif.c:36:12: error: 'tegra20_spdif_runtime_resume' defined but not used [-Werror=unused-function]
> 36 | static int tegra20_spdif_runtime_resume(struct device *dev)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> tegra/tegra20_spdif.c:27:12: error: 'tegra20_spdif_runtime_suspend' defined but not used [-Werror=unused-function]
> 27 | static int tegra20_spdif_runtime_suspend(struct device *dev)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> tegra/tegra30_ahub.c:64:12: error: 'tegra30_ahub_runtime_resume' defined but not used [-Werror=unused-function]
> 64 | static int tegra30_ahub_runtime_resume(struct device *dev)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> tegra/tegra30_ahub.c:43:12: error: 'tegra30_ahub_runtime_suspend' defined but not used [-Werror=unused-function]
> 43 | static int tegra30_ahub_runtime_suspend(struct device *dev)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: tegra: mark runtime-pm functions as __maybe_unused
commit: ccd4cc3ed0692aef8a3b4566391c37eb168d8d32
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
Powered by blists - more mailing lists