All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Scott Davilla <davilla@4pi.com>,
	Naren Sankar <nsankar@broadcom.com>,
	Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [PATCH v3] staging: add Broadcom Crystal HD driver
Date: Mon, 04 Jan 2010 18:34:13 -0500	[thread overview]
Message-ID: <4B427AF5.2030805@redhat.com> (raw)
In-Reply-To: <20100104231949.GA14496@kroah.com>

On 1/4/10 6:19 PM, Greg KH wrote:
> On Mon, Jan 04, 2010 at 06:02:27PM -0500, Jarod Wilson wrote:
>> This patch supersedes the earlier ones sent by Manu Abraham to add
>> the Broadcom Crystal HD driver to the staging tree, per discussion
>> with him about it. I've been working with Broadcom's Naren Sankar
>> on this driver for a number of months, and had already talked Naren
>> about submitting this on Broadcom's behalf, didn't expect anyone
>> else to jump on submitting it as quickly as Manu did. ;)
> 
> Looks good, I'll queue it up tomorrow.

Nb: it looks like the thing is so massive (~935k), its not showing up on
lkml (at least, not in a timely fashion), so for the interested:

<http://people.redhat.com/jwilson/misc/broadcom-crystalhd-decoder-driver-staging.patch>

Thanks much!

-- 
Jarod Wilson
jarod@redhat.com

  reply	other threads:[~2010-01-04 23:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100104230227.GA14314@redhat.com>
2010-01-04 23:19 ` [PATCH v3] staging: add Broadcom Crystal HD driver Greg KH
2010-01-04 23:34   ` Jarod Wilson [this message]
2010-01-05  2:21     ` Robert Hancock
2010-01-05  2:36       ` Naren (Narendra) Sankar
2010-01-05  6:58         ` Jarod Wilson
2010-01-05  7:05 Naren (Narendra) Sankar
2010-01-05  7:10 ` Jarod Wilson
2010-01-05 14:45   ` 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=4B427AF5.2030805@redhat.com \
    --to=jarod@redhat.com \
    --cc=abraham.manu@gmail.com \
    --cc=davilla@4pi.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsankar@broadcom.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.