linux-kernel - Re: [PATCH] ASoC: amd: fixed kernel warnings

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: <159422758800.28431.7689040196790188529.b4-ty@kernel.org>
Date:   Wed, 08 Jul 2020 18:00:20 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc:     Takashi Iwai <tiwai@...e.com>,
        open list <linux-kernel@...r.kernel.org>,
        rdunlap@...radead.org, Alexander.Deucher@....com,
        Liam Girdwood <lgirdwood@...il.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Subject: Re: [PATCH] ASoC: amd: fixed kernel warnings

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