From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH, RTF/RFC] bcm43xx: Enable local IRQs while executing periodic work
Date: Mon, 5 Jun 2006 14:54:38 -0400 [thread overview]
Message-ID: <20060605185433.GF6068@tuxdriver.com> (raw)
In-Reply-To: <200605231723.10028.mb@bu3sch.de>
On Tue, May 23, 2006 at 05:23:09PM +0200, Michael Buesch wrote:
> I would like to get this into wireless-2.6, but before that
> happens I would like to have a few regression tests by people.
> Please apply this and run high network traffic for 10-15 minutes.
> Please enable kernel spinlock lockup and recursion detection
> while testing.
It has almost been two weeks...do we want this patch, or not?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-06-05 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 15:23 [PATCH, RTF/RFC] bcm43xx: Enable local IRQs while executing periodic work Michael Buesch
2006-06-05 18:54 ` John W. Linville [this message]
[not found] ` <20060605185433.GF6068-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2006-06-05 19:13 ` Michael Buesch
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=20060605185433.GF6068@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
/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).