From: Zhu Yi <yi.zhu@intel.com>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Tomas Winkler <tomasw@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Subject: Re: pull request: wireless-2.6 2008-11-18
Date: Mon, 24 Nov 2008 14:33:14 +0800 [thread overview]
Message-ID: <1227508394.2548.307.camel@debian.sh.intel.com> (raw)
In-Reply-To: <7E134DC0-A86D-460A-B5DC-22E6D9BEED92@linux.intel.com>
On Mon, 2008-11-24 at 11:50 +0800, Marcel Holtmann wrote:
> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703
>
> and just relying on Bugzilla is not gonna be good enough. The Linux
> kernel development has always been done via mailing lists. And while
> there is a kernel and other Bugzillas, the main authority is still the
> mailing list. So if you wanna get massive feedback or have testing
> patches for debugging, then these need to be posted to linux-wireless
> and not "hidden" into a Bugzilla.
This is generally true for bugs easy to debug with. But in this example,
the first reporter opened this bug 4 months ago. People usually don't
follow thread for such a long time. There are also some reporters never
show up in this ML.
> I do have a perfect environment in Vancouver that allows me to trigger
> this behavior within a few minutes. So if you really wanna debug this,
> then just send debug patches to the mailing list and I am happy to run
> such kernels.
Can you still reproduce this bug with Johannes' patch?
Thanks,
-yi
next prev parent reply other threads:[~2008-11-24 6:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 0:07 pull request: wireless-2.6 2008-11-18 John W. Linville
2008-11-19 1:33 ` Johannes Berg
2008-11-19 1:33 ` Johannes Berg
2008-11-19 1:54 ` John W. Linville
2008-11-19 1:54 ` John W. Linville
2008-11-19 6:46 ` Tomas Winkler
2008-11-19 9:34 ` Tomas Winkler
2008-11-19 14:39 ` John W. Linville
2008-11-19 14:39 ` John W. Linville
2008-11-19 16:51 ` Tomas Winkler
2008-11-19 16:51 ` Tomas Winkler
2008-11-19 18:53 ` John W. Linville
2008-11-19 18:53 ` John W. Linville
2008-11-19 21:55 ` Tomas Winkler
2008-11-19 21:55 ` Tomas Winkler
2008-11-20 0:37 ` John W. Linville
2008-11-20 0:37 ` John W. Linville
2008-11-20 9:27 ` Tomas Winkler
2008-11-20 9:27 ` Tomas Winkler
2008-11-24 3:34 ` Zhu Yi
2008-11-24 3:50 ` Marcel Holtmann
2008-11-24 6:33 ` Zhu Yi [this message]
2008-11-24 8:33 ` Marcel Holtmann
2008-11-24 8:33 ` Marcel Holtmann
2008-11-20 12:05 ` David Miller
2008-11-20 12:05 ` David Miller
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=1227508394.2548.307.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=davem@davemloft.net \
--cc=holtmann@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tomasw@gmail.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.