From: Michael Buesch <mb@bu3sch.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>, Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org
Subject: Re: [PATCH dscape] d80211: Switch d80211.h to IEEE80211_ style names
Date: Sat, 5 Aug 2006 19:47:43 +0200 [thread overview]
Message-ID: <200608051947.44280.mb@bu3sch.de> (raw)
In-Reply-To: <200608051930.55792.mb@bu3sch.de>
On Saturday 05 August 2006 19:30, Michael Buesch wrote:
> On Saturday 05 August 2006 13:46, Christoph Hellwig wrote:
> > On Tue, Aug 01, 2006 at 08:21:49AM -0400, John W. Linville wrote:
> > > I don't anticipate the d80211 naming conventions to ever make it out
> > > of wireless-dev. By the time we are ready to push that stuff upstream,
> > > we will have cleaned-up our messes.
> >
> > Yes, absolutely.
> >
> > > This does raise the question: Should we start taking patches to
> > > wireless-dev that migrate the current (i.e. ieee80211/softmac) stack
> > > out of the kernel? This would include (re-)moving the current stack
> > > code, pointing non-migrated drivers (ipw2[12]00, zd1211rw) at the old
> > > code, moving drivers out of drivers/net/wireless/d80211 up a level,
> > > removing the softmac-based version of the bcm43xx driver, etc.
>
> Yes, I personally would like to see that happen now.
I forgot to say why ;)
It's getting a major pain to support two up-to-date bcm43xx drivers.
It's getting nontrivial to port drivers over from bcm43xx-softmac
to bcm43xx-d80211; even with tools like quilt and wiggle.
What I'd like to see is: After 2.6.18 got out, we freeze bcm43xx-softmac
and only allow small bugfixes to it. All development work would go
into the d80211 branch.
That saves me a _lot_ of time and pain.
--
Greetings Michael.
next prev parent reply other threads:[~2006-08-05 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 7:37 [PATCH dscape] d80211: Switch d80211.h to IEEE80211_ style names Michael Wu
2006-07-31 20:31 ` John W. Linville
2006-07-31 20:51 ` Michael Wu
2006-08-01 9:56 ` Christoph Hellwig
2006-08-01 12:21 ` John W. Linville
2006-08-01 13:58 ` Jiri Benc
2006-08-01 14:07 ` John W. Linville
2006-08-01 14:25 ` Ivo Van Doorn
2006-08-01 17:11 ` John W. Linville
2006-08-01 17:31 ` Ivo van Doorn
2006-08-01 19:13 ` Ulrich Kunitz
2006-08-05 11:46 ` Christoph Hellwig
2006-08-05 17:30 ` Michael Buesch
2006-08-05 17:47 ` Michael Buesch [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 6:02 Michael Wu
2006-07-26 16:32 ` Jiri Benc
2006-07-26 16:43 ` Michael Wu
2006-07-26 16:53 ` Jiri Benc
2006-07-26 17:10 ` Michael Wu
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=200608051947.44280.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=flamingice@sourmilk.net \
--cc=hch@infradead.org \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).