From: Greg KH <greg@kroah.com>
To: Joe Perches <joe@perches.com>
Cc: Vipin Mehta <vmehta@atheros.com>,
Vipin Mehta <Vipin.Mehta@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH 00/83] staging: ath6kl: Style cleanup
Date: Sun, 23 Jan 2011 01:32:32 -0800 [thread overview]
Message-ID: <20110123093232.GA29967@kroah.com> (raw)
In-Reply-To: <1295742255.21754.3.camel@Joe-Laptop>
On Sat, Jan 22, 2011 at 04:24:15PM -0800, Joe Perches wrote:
> On Fri, 2011-01-21 at 13:16 -0800, Greg KH wrote:
> > I need this series against the proper branch, if I am going to be able
> > to apply them.
>
> I am working on this major style rewrite of ath6kl right now.
>
> Please do not apply new patches to ath6kl this upcoming week
> as it takes quite a bit of work to resync and validate 100+
> patches.
Sorry, but that's not how you do things. Nor is it how I do things, if
people send me patches, I take them in the order in which they arrive.
NEVER send 100+ patches, send out what you have, when you have them,
which makes stuff like this, much easier to handle.
And wasn't this driver just a "placeholder" while a "real" driver was
being written?
good luck,
greg k-h
prev parent reply other threads:[~2011-01-23 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 19:23 [PATCH 00/83] staging: ath6kl: Style cleanup Vipin Mehta
2011-01-21 19:38 ` Greg KH
2011-01-21 19:43 ` Joe Perches
2011-01-21 19:48 ` Vipin Mehta
2011-01-21 19:55 ` Greg KH
2011-01-21 20:09 ` Vipin Mehta
2011-01-21 21:16 ` Greg KH
2011-01-23 0:24 ` Joe Perches
2011-01-23 9:32 ` 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=20110123093232.GA29967@kroah.com \
--to=greg@kroah.com \
--cc=Vipin.Mehta@Atheros.com \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vmehta@atheros.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;
as well as URLs for NNTP newsgroup(s).