Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k_htc: fix skb_under_panic error
Date: Thu, 06 Jun 2013 14:06:11 +0200	[thread overview]
Message-ID: <51B07B33.2060207@rempel-privat.de> (raw)
In-Reply-To: <CAGXE3d-kg7k=R81mKcqMfM9FFBDn0A9RNYmuTdQHXRUX37QhsA@mail.gmail.com>

Am 06.06.2013 13:48, schrieb Helmut Schaa:
> On Wed, Jun 5, 2013 at 7:03 PM, Oleksij Rempel <linux@rempel-privat.de> wrote:
>> I was running two stream netperf test for 2 hours without visible
>> regressions.
>
> With or without your pskb_expand_head patch applied?
>
> Thanks,
> Helmut
>

whithout my patch, on to of wireless-testing master git. But i didn't 
had this problem before. So, may be this scenario was not used by me.
Shouldn't we actually have this check from my patch, to avoid other oopses?

-- 
Regards,
Oleksij

  reply	other threads:[~2013-06-06 12:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <519D405B.2080806@blackshift.org>
2013-05-24  8:47 ` [ath9k-devel] skb_under_panic in ath9k Marc Kleine-Budde
2013-05-26  6:20   ` Oleksij Rempel
2013-05-26  8:02     ` [ath9k-devel] [PATCH RFC] " Oleksij Rempel
2013-06-04 10:05       ` Marc Kleine-Budde
2013-06-04 18:37         ` [ath9k-devel] [PATCH] ath9k_htc: fix skb_under_panic error Oleksij Rempel
2013-06-05  8:54           ` Helmut Schaa
2013-06-05 14:24           ` Helmut Schaa
2013-06-05 14:26             ` Marc Kleine-Budde
2013-06-05 14:46               ` Oleksij Rempel
2013-06-05 17:03                 ` Oleksij Rempel
2013-06-06 11:48                   ` Helmut Schaa
2013-06-06 12:06                     ` Oleksij Rempel [this message]
2013-08-16 19:32             ` Marc Kleine-Budde
2013-06-04 10:09 ` [ath9k-devel] skb_under_panic in ath9k Marc Kleine-Budde

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=51B07B33.2060207@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=ath9k-devel@lists.ath9k.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