From: Arjan van de Ven <arjan@infradead.org>
To: "Bob Copeland" <me@bobcopeland.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mcgrof@gmail.com, mickflemm@gmail.com
Subject: Re: pull request: wireless-2.6 2008-10-29
Date: Wed, 29 Oct 2008 21:00:05 -0700 [thread overview]
Message-ID: <20081029210005.48e4765f@infradead.org> (raw)
In-Reply-To: <b6c5339f0810291819ld7d6043k56b11128bc6252cb@mail.gmail.com>
On Wed, 29 Oct 2008 21:19:01 -0400
"Bob Copeland" <me@bobcopeland.com> wrote:
> On Wed, Oct 29, 2008 at 7:33 PM, John W. Linville
> <linville@tuxdriver.com> wrote:
> > On Wed, Oct 29, 2008 at 04:23:24PM -0700, Arjan van de Ven wrote:
> >> On Wed, 29 Oct 2008 19:18:55 -0400
> >> "John W. Linville" <linville@tuxdriver.com> wrote:
> >> it seems to have added a few WARN_ON()s which now end up at the
> >> top of the list .. are these known or should I spend some time
> >> writing reports for netdev ?
>
> Pavel Roskin posted one such WARN_ON to ath5k-devel a few days ago.
> Seems related to setup of the rate tables, but I haven't reproduced it
> here yet. I'll see if he has more info...
if there's things that would help you diagnose such issue let me know
(always trying to make kerneloops.org more useful for developers ;-)
>
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-30 3:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 23:18 pull request: wireless-2.6 2008-10-29 John W. Linville
2008-10-29 23:23 ` Arjan van de Ven
2008-10-29 23:33 ` John W. Linville
2008-10-30 1:19 ` Bob Copeland
2008-10-30 4:00 ` Arjan van de Ven [this message]
2008-10-30 14:48 ` Stefan Hellermann
2008-10-30 16:17 ` Bob Copeland
2008-10-29 23:40 ` Elias Oltmanns
2008-10-31 6:49 ` 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=20081029210005.48e4765f@infradead.org \
--to=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--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).