linux-kernel - Re: [PATCH] staging: Merge Crystal HD driver with linuxtv.org

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: <20131027162613.GA23822@kroah.com>
Date:	Sun, 27 Oct 2013 09:26:13 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Steven Newbury <steve@...wbury.org.uk>
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 Sun, Oct 27, 2013 at 05:12:18PM +0000, Steven Newbury wrote:
> > And these patches do a lot of new work to the driver, I'd rather see it
> > get fixed up properly and moved out of staging first, before adding new
> > support to it, otherwise why is it in staging at all?
> 
> That last part it a good question, it's been sitting there for 3 years,
> I assume there are specific things that need improving to get it out of
> staging?  Would the changes in this patch, without the support for new
> hw support be sufficient to get that to happen?  I can't test it without
> that support though...

See the TODO file for a list of things that need to be resolved.

I've been remiss in deleting some of the staging drivers lately, and
this one was on my shortlist for removal, but if you have hardware for
it, and want to adopt it, I'll gladly take the patches for getting your
stuff to work if you are going to work toward getting it out of staging.

thanks,

greg k-h
--
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/