linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <larry.finger@lwfinger.net>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	linux-wireless@vger.kernel.org, Joe Jezak <josejx@gentoo.org>,
	Daniel Drake <dsd@gentoo.org>
Subject: Re: [PATCH] softmac: use list_for_each_entry
Date: Mon, 11 Jun 2007 16:06:29 -0400	[thread overview]
Message-ID: <20070611200629.GH10397@tuxdriver.com> (raw)
In-Reply-To: <20070611191854.GG10397@tuxdriver.com>

On Mon, Jun 11, 2007 at 03:18:54PM -0400, John W. Linville wrote:

> Plus, we may need to consider preserving the driver in its current
> form (aside from the softmac -> mac80211 port) for some time as a
> compatibility aid for those who already have working configurations
> with the "bcm43xx" driver.  Forcing a happy user to locate new firmware
> for no obvious benefit to them is not very nice (as I have learned
> so well w/ Fedora 7)...

As a re-read this, it seems subject to misinterpretation.  I mean
that once the existing bcm43xx driver (11g bits and all) is ported to
mac80211, we may want to keep the 11g bits even after the existing
bcm43xx-mac80211 (using v4 firmware) driver has been ported.
Worth considering...

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

  reply	other threads:[~2007-06-11 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27 14:27 [PATCH] softmac: use list_for_each_entry Akinobu Mita
2007-05-31 20:24 ` Johannes Berg
2007-06-01 15:59   ` Larry Finger
2007-06-01 19:12     ` Johannes Berg
2007-06-11 19:18       ` John W. Linville
2007-06-11 20:06         ` John W. Linville [this message]
2007-06-11 20:14         ` Larry Finger

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=20070611200629.GH10397@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=akinobu.mita@gmail.com \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=josejx@gentoo.org \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@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).