All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: devel@driverdev.osuosl.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 0/3] Move media staging drivers to staging/media
Date: Wed, 2 Nov 2011 08:10:09 -0700	[thread overview]
Message-ID: <20111102151009.GA22699@suse.de> (raw)
In-Reply-To: <20111102094509.4954fead@redhat.com>

On Wed, Nov 02, 2011 at 09:45:09AM -0200, Mauro Carvalho Chehab wrote:
> Greg,
> 
> As agreed, this is the patches that move media drivers to their
> own places. Basically, cx25821 now seems ready to be at the standard
> place, while the other drivers should still be in staging for a while.
> 
> The cxd2099 is a special case. This is an optional driver for handling
> encrypted DVB streams. It abuses of the DVB API and, while we don't
> have a proper way for handling it, we should keep it at staging, as
> its API will change after we add proper support for it. According with
> KS Workshop discussions, the proper way seems to add Media Controller
> capabilities for DVB, and allow changing the DVB pipelines to add
> a decriptor if/when needed.
> 
> PS.: I'll likely merge patch 3 with patch 2 when submitting it
> upstream.

That would be great, please feel free to add:
	Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
to all of these and send them to Linus through your tree.

thanks,

greg k-h

  reply	other threads:[~2011-11-02 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 11:45 [PATCH 0/3] Move media staging drivers to staging/media Mauro Carvalho Chehab
2011-11-02 15:10 ` Greg KH [this message]
2011-11-17 17:47   ` Tomas Winkler
2011-11-17 18:09     ` Greg KH
2011-11-17 19:10       ` Tomas Winkler
2011-11-17 19:22         ` Greg KH

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=20111102151009.GA22699@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    /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.