linux-kernel - Re: DA9063 driver development

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]

Date:	Fri, 6 Sep 2013 12:20:28 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Steve Twiss <stwiss.opensource@...semi.com>
Cc:	Philipp Zabel <p.zabel@...gutronix.de>,
	Lee Jones <lee.jones@...aro.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: DA9063 driver development

On Fri, Sep 06, 2013 at 10:47:58AM +0000, Steve Twiss wrote:

> Is it possible to remove this driver from linux-next so these issues 
> can be resolved by Dialog?

No, sorry.  The regulator tree has already been merged into Linus' tree
for v3.12 so can't be changed now.

In any case the best approach to a situation like this is to make
incremental improvements to the code in mainline rather than just throw
out the existing code and start over.  This ensures that no work done on
the mainline version during or after merge gets lost.  The best way to
avoid this happening is to submit drivers as soon as you can, and of
course to make sure that any code sent to mainline is reviewed.

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