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:	Tue, 29 Oct 2013 14:51:00 +0000
From:	Steven Newbury <steve@...wbury.org.uk>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, Naren Sankar <nsankar@...adcom.com>,
	Jarod Wilson <jarod@...sonet.com>,
	Scott Davilla <davilla@....com>,
	Manu Abraham <abraham.manu@...il.com>
Subject: Re: [PATCH] staging: Merge Crystal HD driver with linuxtv.org

On Tue, 2013-10-29 at 12:54 +0000, Steven Newbury wrote:
> Hi Greg,
> I'm making good progress.  My plan is to break/clean up the patch
> logically:
> 
> patch1: Clean up debug/error messages  DONE - (this has actually
> resulted in some bug fixes)
> 
<- patch1b: Clean up typedefs (missed this in my list, but it's what I'm
working on right now) WIP

> patch2: Remove commented out/unused code  TODO
> 
> patch3: Power management support  TODO
> 
> patch4: other misc fixes/changes (may be more than one patch) with
> details in log message
> 
> patch5: Rename driver to crystalhd (instead of bcm70012) DONE
> 
> patch6: Restructure driver to prepare for BCM70015 support by splitting
> out (BCM70012) hw specific parts.  DONE
> 
> patch7: Add BCM70015 support  MOSTLY DONE - some clean up needed
> 
> 
> To me this makes more sense than trying to apply the patches as applied
> to the linuxtv.org git repo since there's a lot of irrelevant code churn
> and changes in commits which are undocumented in the log message along
> with the fact they won't apply cleanly on top of the existing staging
> driver anyway.



--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ