linux-kernel - Re: [PATCH] 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: <20130619193652.GJ1403@sirena.org.uk>
Date:	Wed, 19 Jun 2013 20:36:52 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Oleksandr Kozaruk <oleksandr.kozaruk@...com>
Cc:	tony@...mide.com, sameo@...ux.intel.com, lgirdwood@...il.com,
	grant.likely@...aro.org, rob.herring@...xeda.com, rob@...dley.net,
	t-kristo@...com, gg@...mlogic.co.uk, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	linux-omap@...r.kernel.org
Subject: Re: [PATCH] MFD: Change TWL6025 references to TWL6032

On Wed, Jun 19, 2013 at 03:24:02PM +0300, Oleksandr Kozaruk wrote:

> There are non-mainline branches that use twl6032 by its name (for example
> git://git.omapzoom.org/kernel/omap.git). There is intention to add support
> of twl6032 device in mainline, but we'd like to know if we can use twl6032
> instead of twl6025 in our new patches, that we are going to provide.
> Related discussion: https://patchwork.kernel.org/patch/2686331/

It's always been OK to use the new name, the only question was if it was
better to keep the old name supported as well.  Given that the chips are
essentially nonexistant now your current approach seems sensible so

Reviwed-by: Mark Brown <broonie@...aro.org>

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