linux-kernel - Re: [PATCH v2] hwmon: Introduce the use of the managed version of kzalloc

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: <20140520232029.2631e56b@endymion.delvare>
Date:	Tue, 20 May 2014 23:20:29 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Himangi Saraogi <himangi774@...il.com>, lm-sensors@...sensors.org,
	linux-kernel@...r.kernel.org, julia.lawall@...6.fr
Subject: Re: [PATCH v2] hwmon: Introduce the use of the managed version of
 kzalloc

On Tue, 20 May 2014 13:03:36 -0700, Guenter Roeck wrote:
> On Tue, May 20, 2014 at 11:45:37PM +0530, Himangi Saraogi wrote:
> Applied to -next, just for the sake of it, but frankly that driver
> is screwed up so badly that it is pretty much unusable anyway.
> Almost all of its attributes are non-standard, and for most of them
> that is completely unnecsssary.
> 
> Maybe we should create a to-be-removed list and put it there
> as first candidate.

The traditional way for this is to move the driver to drivers/staging,
mention a deadline in the commit message, and delete it after a few
releases if nobody steps up.

An alternative would be to contact the maintainer (or short of that,
the original contributor) of the driver for an update. Again, with a
deadline.

-- 
Jean Delvare
SUSE L3 Support
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/