From: Joe Perches <joe@perches.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Greg KH <gregkh@suse.de>,
linux-wireless@vger.kernel.org,
Kalle Valo <kalle.valo@atheros.com>,
linville@tuxdriver.com, devel@linuxdriverproject.org
Subject: Re: Plan for ath6kl cleanup
Date: Fri, 20 May 2011 09:51:21 -0700 [thread overview]
Message-ID: <1305910281.4209.36.camel@Joe-Laptop> (raw)
In-Reply-To: <20110520142934.GA20250@infradead.org>
On Fri, 2011-05-20 at 10:29 -0400, Christoph Hellwig wrote:
> On Fri, May 20, 2011 at 06:36:00AM -0700, Greg KH wrote:
> > On Fri, May 20, 2011 at 04:13:24PM +0300, Kalle Valo wrote:
> > > We have been thinking about how to get ath6kl out from staging and get
> > > it to a first class citizen under drivers/net/wireless. There's quite a
> > > lot of work to do get ath6kl cleaned up and the prospect of doing all
> > > that through the staging-next tree wasn't that exciting. We would be
> > > sending hundreds of patches and it would take a long time to cleanup the
> > > driver. And the disconnection from the wireless core development also
> > > sounded very daunting (cfg80211 API changes etc.).
> >
> > This sounds like, "We don't like the kernel development model, it
> > requires us to break everything up into small patches and show our work
> > to everyone."
>
> It's not the kernel development mode, it's something that you try to
> impose on staging users. Creating a more less new driver from a pig
> pile of junk doesn't make sense minimized patches with micro-review.
I tried it once on ath6kl.
Ended up with ~300 patches and a very clean tree.
http://repo.or.cz/w/linux-2.6/trivial-mods.git/shortlog/refs/heads/20110108_ath6kl
The coordination with atheros and greg was balky.
next prev parent reply other threads:[~2011-05-20 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:13 Plan for ath6kl cleanup Kalle Valo
2011-05-20 13:36 ` Greg KH
2011-05-20 14:29 ` Christoph Hellwig
2011-05-20 16:51 ` Joe Perches [this message]
2011-05-21 3:11 ` Greg KH
2011-05-20 14:33 ` Kalle Valo
2011-05-21 5:24 ` Dan Carpenter
2011-05-20 14:26 ` Marcel Holtmann
2011-05-20 14:45 ` Kalle Valo
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=1305910281.4209.36.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=kalle.valo@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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