linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: Advice regarding mac80211 bug
Date: Mon, 28 Jan 2008 13:06:12 -0500	[thread overview]
Message-ID: <20080128180612.GE5835@tuxdriver.com> (raw)
In-Reply-To: <479A858F.9030601@lwfinger.net>

On Fri, Jan 25, 2008 at 05:57:51PM -0700, Larry Finger wrote:

> Now that 2.6.24 has been released, this bug will be propagating into mainline in 2.6.25-rcX and many
> more systems may crash as a result. My question is as follows: Should I submit the band-aid patch
> now while still looking for a better solution, or wait?

Sorry I didn't get back to you sooner.  I think you handled it fine.

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

      reply	other threads:[~2008-01-28 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  0:57 Advice regarding mac80211 bug Larry Finger
2008-01-28 18:06 ` John W. Linville [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=20080128180612.GE5835@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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).