netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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: Tue, 1 Aug 2006 08:21:49 -0400	[thread overview]
Message-ID: <20060801122142.GB29208@tuxdriver.com> (raw)
In-Reply-To: <20060801095650.GA6831@infradead.org>

On Tue, Aug 01, 2006 at 10:56:50AM +0100, Christoph Hellwig wrote:
> On Mon, Jul 31, 2006 at 01:51:31PM -0700, Michael Wu wrote:
> > On Monday 31 July 2006 13:31, John W. Linville wrote:
> > > As usual I'll depend on Jiri to merge d80211 stack patches, then
> > > send me a pull request.  If I apply your "Switch drivers to d80211"
> > > series now, that will undoutedly cause a breakage when Jiri asks me
> > > to pull this later.
> > >
> > Yeah, there needs to be a new (and smaller) set of patches to switch drivers 
> > to the d80211.h header.
> 
> NACK again.  Driver should continue to use the ieee80211.h header forever.

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.

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.

Are we ready for this?  Who wants to be the wireless janitor?

Whether Michael's patches come before or after this clean-up
really doesn't matter.  I'd probably rather have them now.  It only
complicates the migration slightly, while accomplishing something
useful.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2006-08-01 12:22 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 [this message]
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
  -- 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=20060801122142.GB29208@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=flamingice@sourmilk.net \
    --cc=hch@infradead.org \
    --cc=jbenc@suse.cz \
    --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).