All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Newbury <steve@snewbury.org.uk>
Cc: linux-kernel@vger.kernel.org, Naren Sankar <nsankar@broadcom.com>,
	Jarod Wilson <jarod@wilsonet.com>,
	Scott Davilla <davilla@4pi.com>,
	Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [PATCH] staging: Merge Crystal HD driver with linuxtv.org
Date: Sun, 27 Oct 2013 09:26:13 -0700	[thread overview]
Message-ID: <20131027162613.GA23822@kroah.com> (raw)
In-Reply-To: <1382893938.2598.24.camel@artifact>

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

  reply	other threads:[~2013-10-27 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 16:27 [PATCH] staging: Merge Crystal HD driver with linuxtv.org Steven Newbury
2013-10-27 15:54 ` Greg KH
2013-10-27 17:12   ` Steven Newbury
2013-10-27 16:26     ` Greg KH [this message]
2013-10-27 18:15       ` Steven Newbury
2013-10-29 12:54         ` Steven Newbury
2013-10-29 14:51           ` Steven Newbury

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131027162613.GA23822@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abraham.manu@gmail.com \
    --cc=davilla@4pi.com \
    --cc=jarod@wilsonet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsankar@broadcom.com \
    --cc=steve@snewbury.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.