All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: What made this bug report better? (was Re: Poking ieee80211_default_rc_algo causes kernel lockups)
Date: Tue, 24 Feb 2009 13:43:22 +1030	[thread overview]
Message-ID: <200902241343.22762.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090220102705.GA2884@silver.sucs.org>

On Friday 20 February 2009 20:57:05 Sitsofe Wheeler wrote:
> What happened this time that made things succesful? Was the original
> mail too big? Did it not make it to the list?

Frederic was the difference; he pulled me in by CC'ing me, once he figured
out it was my bug.

Cheers,
Rusty.

  parent reply	other threads:[~2009-02-24  3:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15 16:09 Poking ieee80211_default_rc_algo causes kernel lockups Sitsofe Wheeler
2009-02-15 17:02 ` Frederic Weisbecker
2009-02-15 19:24   ` Sitsofe Wheeler
2009-02-15 19:41     ` Frederic Weisbecker
2009-02-15 21:02       ` Sitsofe Wheeler
2009-02-16  1:40         ` Frederic Weisbecker
2009-02-16  2:37           ` Frederic Weisbecker
2009-02-15 19:35 ` Frederic Weisbecker
2009-02-16 10:10   ` Rusty Russell
2009-02-16 17:59     ` Frederic Weisbecker
2009-02-16 23:37       ` Rusty Russell
2009-02-20 10:27         ` What made this bug report better? (was Re: Poking ieee80211_default_rc_algo causes kernel lockups) Sitsofe Wheeler
2009-02-20 11:31           ` Ingo Molnar
2009-02-24  3:13           ` Rusty Russell [this message]
2009-02-24  8:16             ` What made this bug report better? Sitsofe Wheeler
2009-02-24 17:58               ` Frederic Weisbecker

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=200902241343.22762.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sitsofe@yahoo.com \
    /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.