public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: jarod@wilsonet.com
Cc: Jon Smirl <jonsmirl@gmail.com>,
	Manu Abraham <abraham.manu@gmail.com>,
	Peter Paul <abnominales@web.de>,
	linux-kernel@vger.kernel.org, davilla@4pi.com,
	nsankar@broadcom.com
Subject: Re: [patch staging] BCM70010 (crystalhd) Linux Driver
Date: Sun, 3 Jan 2010 09:34:17 -0800	[thread overview]
Message-ID: <20100103173417.GC9223@kroah.com> (raw)
In-Reply-To: <7cdf10991001022051k2c8454c1q5cffb955e901e58a@mail.gmail.com>

On Sat, Jan 02, 2010 at 11:51:23PM -0500, Jarod Wilson wrote:
> > I'm not against this submission, but would it be better to wait until
> > Monday when the Broadcom authors are back as see if they want to
> > submit their own driver? That way changes would end up back in their
> > internal VCS.
> 
> Yes, please hold off a bit on this, I've actually been working on this
> driver with Scott and Naren (cc'd) for several months now (which is
> part of why it doesn't look so much like a lot of typical vendor code
> ;), and was planning to handle the submission on Naren and Broadcom's
> behalf. Just didn't expect someone else to hop on it this quickly. Was
> planning to get a git tree up on git.kernel.org over the weekend for
> both the driver and the lib, start prepping patches for review, etc.,
> but family time and home improvement projects have taken precedence
> the past few days (not to mention a few other driver projects that
> sucked up time earlier in the break, *cough* IR).

Ok, I'll ignore the patches from Manu for now, but please, do not create
a git tree, just send me what you have right now, as obviously some
people find it useful.  Then, everyone can work on it together in the
main kernel.org tree, like the rest of kernel development is done.

If you have any questions about how to do this, please let me know.

thanks,

greg k-h

      reply	other threads:[~2010-01-03 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 20:06 BCM70010 (crystalhd) Linux Driver Peter Paul
2009-12-31 13:18 ` Andrey Panin
2010-01-01  0:19   ` Greg KH
     [not found]     ` <1a297b361001020805y6b00af83g81cf8492aa73bc3b@mail.gmail.com>
2010-01-02 16:34       ` [patch staging] " Greg KH
2010-01-02 18:17         ` Manu Abraham
2010-01-02 19:21           ` Greg KH
2010-01-02 20:08             ` Manu Abraham
2010-01-02 22:03           ` Jon Smirl
2010-01-02 23:14             ` Manu Abraham
2010-01-03  4:51             ` Jarod Wilson
2010-01-03 17:34               ` Greg KH [this message]

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=20100103173417.GC9223@kroah.com \
    --to=greg@kroah.com \
    --cc=abnominales@web.de \
    --cc=abraham.manu@gmail.com \
    --cc=davilla@4pi.com \
    --cc=jarod@wilsonet.com \
    --cc=jonsmirl@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox