All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: Change schedule for old-fw support removal
Date: Sat, 27 Dec 2008 12:36:16 -0600	[thread overview]
Message-ID: <495675A0.4090602@lwfinger.net> (raw)
In-Reply-To: <200812271826.39910.mb@bu3sch.de>

Michael Buesch wrote:
> The scheduled date for the removal of old fw support was in July 2008.
> However, we're not going to remove the support unless it causes a major
> headache. So change the schedule from "July 2008" to "when it causes headaches".
> 
> Signed-off-by: Michael Buesch <mb@bu3sch.de>

ACK.

Larry

      reply	other threads:[~2008-12-27 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27 17:26 [PATCH] b43: Change schedule for old-fw support removal Michael Buesch
2008-12-27 18:36 ` Larry Finger [this message]

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=495675A0.4090602@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 \
    /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.