linux-kernel - Re: [RFC v1] MFD: Change TWL6025 references to TWL6032

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: <20130607143649.GS31367@sirena.org.uk>
Date:	Fri, 7 Jun 2013 15:36:49 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Oleksandr Kozaruk <oleksandr.kozaruk@...com>
Cc:	linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
	sameo@...ux.intel.com, lgirdwood@...il.com, balbi@...com,
	peter.ujfalusi@...com, t-kristo@...com, tony@...mide.com,
	Graeme Gregory <gg@...mlogic.co.uk>
Subject: Re: [RFC v1] MFD: Change TWL6025 references to TWL6032

On Fri, Jun 07, 2013 at 01:53:10PM +0300, Oleksandr Kozaruk wrote:
> From: Graeme Gregory <gg@...mlogic.co.uk>
> 
> The TWL6025 was never released beyond sample form and was replaced by
> the PhoenixLite range of chips - TWL6032. Change the references to
> reference the TWL6032 class and name the registers to twl6032 in line with
> an actual released chip name to avoid confusion.
> 
> Currently there is no users of TWL6025 in the code. 

Given that the chip exists even if not widely distributed it seems as
well to keep the twl6025 references in there at least in the device ID
table - it won't do any harm to people using the twl6032 name and might
help someone who happens to pick up an old board for whatever reason.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)