public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Peter Paul <abnominales@web.de>, linux-kernel@vger.kernel.org
Subject: Re: [patch staging] BCM70010 (crystalhd) Linux Driver
Date: Sat, 2 Jan 2010 08:34:49 -0800	[thread overview]
Message-ID: <20100102163449.GB5172@kroah.com> (raw)
In-Reply-To: <1a297b361001020805y6b00af83g81cf8492aa73bc3b@mail.gmail.com>

On Sat, Jan 02, 2010 at 08:05:38PM +0400, Manu Abraham wrote:
> Hi Greg,
> 
> > I'm glad to do so if someone wants to help work on it there and shephard
> > it into the main kernel tree.
> 
> Please find the initial round of cleaned up patches for staging,
> applied against linux-next.

Did you really author this driver?  If so, that's fine, just checking.
If not, please put the correct authorship "From:" in the patch.

Also, please break up patches to be sent one-per-email so they can be
properly applied, and also only have them do one thing (your 4th patch
fixed up coding style issues and added the driver to the build.)

Also, can you add a TODO file to the driver directory stating what is
needed to be done, and who to contact about it?

thanks,

greg k-h

  parent reply	other threads:[~2010-01-02 16:40 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       ` Greg KH [this message]
2010-01-02 18:17         ` [patch staging] " 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

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=20100102163449.GB5172@kroah.com \
    --to=greg@kroah.com \
    --cc=abnominales@web.de \
    --cc=abraham.manu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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