linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, jeff@garzik.org, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org, kune@deine-taler.de
Subject: Re: Please pull 'z1211' branch of wireless-2.6
Date: Thu, 20 Sep 2007 15:28:04 +0100	[thread overview]
Message-ID: <46F28374.9040106@gentoo.org> (raw)
In-Reply-To: <20070920134730.GC6748@tuxdriver.com>

John W. Linville wrote:
> I know that you will argue that a rename is unnecessary if we
> simply port the existing driver to mac80211, which is certainly true.
> I just wonder if that is the least bumpy solution for users.  At least
> with a new driver, if something doesn't work then the old driver is
> still there as a fallback.  Plus you can avoid some confusion with
> old howtos and such on the web referring to an old driver instead
> of the new one, etc.  Maybe that isn't a huge issue in this case,
> but I wouldn't underestimate the possible confusion.

Maybe I'll provide a one-off externally building driver for 2.6.25 or 
something like that, just as a basis for comparison. I think biting the 
bullet and simply attacking the issues that come up is the best way.

Old documentation will still be relevant for the mac80211 driver, 
especially if we don't change the driver/config names -- offhand I can't 
think of any obvious differences between the user interface to the 2 
drivers.

>> (just to clarify to others: this is the first I heard of this merge 
>> before John posted it).
> 
> Yes, sorry...permission, forgiveness...forgive? :-)

Of course :)

> If you are determined not to have it in 2.6.24 then I will relent.
> I will also suggest that Larry start sending any softmac bugs to
> you... :-)

That's fine.

> If we will be having a port rather than a new driver, how soon after
> 2.6.24-rc1 closes can we queue the port for 2.6.25?  I think it
> should be almost immediately, to ensure maximum test exposure and to
> "seal the deal".  What do you think?

I think that's realistic, I'll do what I can.

Thanks,
Daniel


  reply	other threads:[~2007-09-20 14:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 18:10 Please pull 'z1211' branch of wireless-2.6 John W. Linville
2007-09-19 18:59 ` David Miller
2007-09-19 19:23   ` Michael Buesch
2007-09-19 19:56     ` David Miller
2007-09-19 20:12       ` David Miller
2007-09-19 22:08 ` Daniel Drake
2007-09-19 22:14   ` David Miller
2007-09-19 22:27     ` Daniel Drake
2007-09-19 22:32       ` David Miller
2007-09-20 13:47   ` John W. Linville
2007-09-20 14:28     ` Daniel Drake [this message]
2007-09-20 16:37       ` Larry Finger
2007-09-20 16:40         ` Johannes Berg
2007-09-22  9:48     ` Ulrich Kunitz
2007-09-22 12:11       ` Michael Buesch
2007-09-22 14:42         ` Ulrich Kunitz
2007-09-22 14:47           ` Michael Buesch
2007-09-19 22:12 ` Daniel Drake
2007-09-20 13:28   ` John W. Linville

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=46F28374.9040106@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=kune@deine-taler.de \
    --cc=linux-wireless@vger.kernel.org \
    --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).