From: Paul Bolle <pebolle@tiscali.nl>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlegacy: print how long queue was actually stuck
Date: Sat, 30 Jun 2012 21:11:21 +0200 [thread overview]
Message-ID: <1341083481.1911.85.camel@x61.thuisdomein> (raw)
In-Reply-To: <CANUX_P3kypkUv+-meABAOGa6GQ9cR5ugySJj+SjvVfCykCQuYQ@mail.gmail.com>
On Sat, 2012-06-30 at 21:18 +0300, Emmanuel Grumbach wrote:
> You may want to try this one:
> http://www.spinics.net/lists/stable-commits/msg18110.html
That issue looks similar, though it regards iwlwifi. Thanks anyway.
Perhaps commit d6ee27eb13beab94056e0de52d81220058ca2297 ("iwlwifi: don't
mess up the SCD when removing a key") can be ported to iwlegacy. We'll
see whether I manage to port it and whether it helps.
Note that iwlwifi also seems to print the (default) timeout in its
message and not how long a queue was actually stuck. So perhaps
something like my patch could be ported to iwlwifi too.
Paul Bolle
next prev parent reply other threads:[~2012-06-30 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 8:36 [PATCH] iwlegacy: print how long queue was actually stuck Paul Bolle
2012-06-30 13:20 ` Paul Bolle
[not found] ` <1341062406.1911.76.camel-uMdlDhfIn7prKue/0VVhAg@public.gmane.org>
2012-06-30 18:18 ` Emmanuel Grumbach
2012-06-30 19:11 ` Paul Bolle [this message]
2012-07-02 9:06 ` Stanislaw Gruszka
2012-07-02 9:32 ` Paul Bolle
[not found] ` <1341221563.1911.141.camel-uMdlDhfIn7prKue/0VVhAg@public.gmane.org>
2012-07-02 9:39 ` Stanislaw Gruszka
2012-07-02 9:53 ` Paul Bolle
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=1341083481.1911.85.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=egrumbach@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox