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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwAxigrSb56OzoyWdAG_Rd9Herw9myS7Yk7aX30BB1qoA@mail.gmail.com>
Date:	Mon, 16 May 2016 19:38:23 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [GIT PULL] regulator updates for v4.7

On Mon, May 16, 2016 at 5:27 AM, Mark Brown <broonie@...nel.org> wrote:
>
> Mark Brown (26):
>       regulator: Deprecate regulator_can_change_voltage()

This needs to be fixed.

It causes a build warning, and it's just not acceptable. We've had
driver subsystems do this before, and then the warning stays around
for years and nothing gets done.

The warning is not just ugly, it ends up often hiding real problems
when people get used to seeing warnings during the build.

The whole "__deprecated" crap has been a bigger problem in itself than
it has ever actually solved.

So don't do it. Either remove bad interfaces or leave them alone. None
of this "let's annoy everybody else with our deprecation messages
whether they care about it or not".

                            Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ