This patch will fix unused variables kernel warnings when
CONFIG_ACPI is disabled.
Reported-by: Randy Dunlap <[email protected]>
Signed-off-by: Vijendar Mukunda <[email protected]>
---
sound/soc/amd/renoir/rn-pci-acp3x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/soc/amd/renoir/rn-pci-acp3x.c b/sound/soc/amd/renoir/rn-pci-acp3x.c
index 165c93f..b943e59 100644
--- a/sound/soc/amd/renoir/rn-pci-acp3x.c
+++ b/sound/soc/amd/renoir/rn-pci-acp3x.c
@@ -168,8 +168,10 @@ static int snd_rn_acp_probe(struct pci_dev *pci,
{
struct acp_dev_data *adata;
struct platform_device_info pdevinfo[ACP_DEVS];
+#if defined(CONFIG_ACPI)
acpi_handle handle;
acpi_integer dmic_status;
+#endif
unsigned int irqflags;
int ret, index;
u32 addr;
--
2.7.4
On 7/7/20 11:37 AM, Vijendar Mukunda wrote:
> This patch will fix unused variables kernel warnings when
> CONFIG_ACPI is disabled.
>
> Reported-by: Randy Dunlap <[email protected]>
> Signed-off-by: Vijendar Mukunda <[email protected]>
Acked-by: Randy Dunlap <[email protected]> # build-tested
Thanks.
> ---
> sound/soc/amd/renoir/rn-pci-acp3x.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/sound/soc/amd/renoir/rn-pci-acp3x.c b/sound/soc/amd/renoir/rn-pci-acp3x.c
> index 165c93f..b943e59 100644
> --- a/sound/soc/amd/renoir/rn-pci-acp3x.c
> +++ b/sound/soc/amd/renoir/rn-pci-acp3x.c
> @@ -168,8 +168,10 @@ static int snd_rn_acp_probe(struct pci_dev *pci,
> {
> struct acp_dev_data *adata;
> struct platform_device_info pdevinfo[ACP_DEVS];
> +#if defined(CONFIG_ACPI)
> acpi_handle handle;
> acpi_integer dmic_status;
> +#endif
> unsigned int irqflags;
> int ret, index;
> u32 addr;
>
--
~Randy
On Wed, 8 Jul 2020 00:07:11 +0530, Vijendar Mukunda wrote:
> This patch will fix unused variables kernel warnings when
> CONFIG_ACPI is disabled.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: amd: fixed kernel warnings
commit: ee3d133972f1e5d260891c4dd58adb005014414a
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