linux-kernel - Re: [PATCH] regulator: rt4801: Fix W=1 build warning when CONFIG

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: <159827590802.48129.16240965662426470036.b4-ty@kernel.org>
Date:   Mon, 24 Aug 2020 14:31:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, cy_huang <u0084500@...il.com>
Cc:     linux-kernel@...r.kernel.org, gene_chen@...htek.com,
        cy_huang@...htek.com
Subject: Re: [PATCH] regulator: rt4801: Fix W=1 build warning when CONFIG_OF=n

On Mon, 24 Aug 2020 10:05:13 +0800, cy_huang wrote:
> Fix below warning when CONFIG_OF=n:
> 
> drivers/regulator/rt4801-regulator.c:206:34: warning: unused variable 'rt4801_of_id' [-Wunused-const-variable]
>   206 | static const struct of_device_id rt4801_of_id[] = {
>       |                                  ^~~~~~~~~~~~

Applied to

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

Thanks!

[1/1] regulator: rt4801: Fix W=1 build warning when CONFIG_OF=n
      commit: c8b2c8949c45b01d75237331fc1387036b952d58

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