linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Stefano Brivio <stefano.brivio@polimi.it>,
	bcm43xx-dev@lists.berlios.de,
	Larry Finger <larry.finger@lwfinger.net>,
	linux-wireless@vger.kernel.org
Subject: Re: schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx
Date: Wed, 21 Nov 2007 19:20:48 +0100	[thread overview]
Message-ID: <200711211920.48640.mb@bu3sch.de> (raw)
In-Reply-To: <20071121135927.GC8792@tuxdriver.com>

On Wednesday 21 November 2007 14:59:27 John W. Linville wrote:
> On Wed, Nov 21, 2007 at 12:26:48AM +0100, Rafael J. Wysocki wrote:
> > On Tuesday, 20 of November 2007, Michael Buesch wrote:
> 
> > > It is known for over a year now that b43 (aka bcm43xx-mac80211) is going to
> > > replace bcm43xx. And we already do a parrallel release cycle with both drivers
> > > included so people can switch. What else do you want?
> > 
> > _First_, mark bcm43xx as unmaintained.  Then, it's not your problem any more.
> > Perhaps there's someone who'd be willing to maintain it.  Otherwise, it will be
> > dropped anyway after some time - when no one uses it any more.  Still, it need
> > not be (and IMHO it shouldn't be) your decision to drop it.
> 
> It is probably true that we haven't communicated this very well
> outside the wireless team.  We probably should have added bcm43xx to
> the feature removal schedule before the 2.6.24 merge window closed.
> 
> How about if we mark bcm43xx as "Obsolete" in MAINTAINERS and add
> an entry to Documentation/feature-removal-schedule.txt with a "When"
> of 2.6.26?  I think that should give everyone sufficient notice...?

So, is SoftMAC already scheduled?
Otherwise, I think when we are about to remove bcm43xx in 2.6.25 someone
is going to complain that removal of softmac was not scheduled...

Btw: Does someone actually read that feature-removal-schedule.txt file?

-- 
Greetings Michael.

  parent reply	other threads:[~2007-11-21 18:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 19:21 [PATCH v3] remove bcm43xx Stefano Brivio
2007-11-19 22:00 ` Rafael J. Wysocki
2007-11-19 22:19   ` Stefano Brivio
2007-11-19 22:36     ` Andreas Schwab
2007-11-19 23:02       ` Rafael J. Wysocki
2007-11-19 23:13       ` Stefano Brivio
2007-11-19 23:19         ` Andreas Schwab
2007-11-20  0:15           ` Stefano Brivio
2007-11-20  9:58             ` Andreas Schwab
2007-11-20 15:09               ` Larry Finger
2007-11-20 15:18                 ` Michael Buesch
2007-11-20 13:17       ` Johannes Berg
2007-11-20 14:07       ` Michael Buesch
2007-11-20 14:11         ` Andreas Schwab
2007-11-20 14:20           ` Michael Buesch
2007-11-20 14:24             ` Andreas Schwab
2007-11-20 14:47             ` Andreas Schwab
2007-11-21  0:25               ` Asheesh Laroia
2007-11-19 22:57     ` Rafael J. Wysocki
2007-11-20  2:33       ` Larry Finger
2007-11-20 13:18       ` Johannes Berg
2007-11-20 14:09       ` Michael Buesch
2007-11-20 23:26         ` Rafael J. Wysocki
2007-11-21 13:45           ` Michael Buesch
2007-11-21 13:59           ` schedule bcm43xx removal for 2.6.26 -- " John W. Linville
2007-11-21 14:16             ` [PATCH] bcm43xx: mark as obsolete and schedule for removal John W. Linville
2007-11-21 15:26               ` [PATCH v2] " John W. Linville
2007-11-21 15:46                 ` Stefano Brivio
2007-11-21 15:00             ` schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx Larry Finger
2007-11-21 15:39               ` Johannes Berg
2007-11-21 18:20             ` Michael Buesch [this message]
2007-11-21 20:26               ` [PATCH] softmac: mark as obsolete and schedule for removal John W. Linville
2007-11-21 19:35             ` schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx Rafael J. Wysocki

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=200711211920.48640.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rjw@sisk.pl \
    --cc=stefano.brivio@polimi.it \
    /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).