On Wednesday, 21 of November 2007, 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?

This is a very good idea IMO.

> I think that should give everyone sufficient notice...? 

Please also state very clearly in the changelog that you'd like to drop the
driver entirely before 2.6.26.

Thanks,
Rafael
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to