From: Larry Finger <larry.finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Michael Buesch <mb@bu3sch.de>,
Stefano Brivio <stefano.brivio@polimi.it>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx
Date: Wed, 21 Nov 2007 09:00:53 -0600 [thread overview]
Message-ID: <47444825.4070505@lwfinger.net> (raw)
In-Reply-To: <20071121135927.GC8792@tuxdriver.com>
John W. Linville wrote:
>
> 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...?
This sounds good to me. Of course, we all understand that once 2.6.25 is released, _EVERY_
complaint/bug report for bcm43xx and SoftMAC will get the response "switch to 2.6.25"!
Larry
next prev parent reply other threads:[~2007-11-21 15:01 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 ` Larry Finger [this message]
2007-11-21 15:39 ` schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx Johannes Berg
2007-11-21 18:20 ` Michael Buesch
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=47444825.4070505@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.