From: Zhu Yi <yi.zhu@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Dan Williams <dcbw@redhat.com>,
Ralf Baechle <ralf@linux-mips.org>,
netdev@vger.kernel.org, Stefan Rompf <stefan@loplof.de>,
James Ketrenos <jketreno@linux.intel.com>,
Patrick McHardy <kaber@trash.net>, jamal <hadi@cyberus.ca>
Subject: Re: ipw2200: Driver lockup
Date: Thu, 20 Jul 2006 13:22:34 +0800 [thread overview]
Message-ID: <1153372954.3485.7.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20060720025810.GA5901@tuxdriver.com>
On Wed, 2006-07-19 at 22:58 -0400, John W. Linville wrote:
> For what it is worth, there was a patch for this posted back
> in January. It stirred-up a kerfluffle, so it never got merged.
> FWIW, it touches on 802.11e QoS and multiple TX queues -- my personal
> favorite wireless subject...NOT!
>
> The thread is available here (first post not connected to follow-up
> thread for some reason):
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=113809246102858&w=2
> http://marc.theaimsgroup.com/?l=linux-netdev&m=113814103024576&w=2
>
> Given that half a year has passed, does anyone have any better ideas
> now? Should I merge the patch? Or is the cure worse than the disease?
The patch from Stefan Rompf in the second link has already been merged.
The first one was already merged (with slightly difference). We can just
remove the ieee80211 warning now.
[PATCH] ieee80211: remove ieee80211_tx() is_queue_full warning
Signed-off-by: Zhu Yi <yi.zhu@intel.com>
---
--- a/net/ieee80211/ieee80211_tx.c
+++ b/net/ieee80211/ieee80211_tx.c
@@ -533,13 +533,6 @@ int ieee80211_xmit(struct sk_buff *skb,
return 0;
}
- if (ret == NETDEV_TX_BUSY) {
- printk(KERN_ERR "%s: NETDEV_TX_BUSY returned; "
- "driver should report queue full via "
- "ieee_device->is_queue_full.\n",
- ieee->dev->name);
- }
-
ieee80211_txb_free(txb);
}
prev parent reply other threads:[~2006-07-20 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 14:28 ipw2200: Driver lockup Ralf Baechle
2006-07-20 0:49 ` Dan Williams
2006-07-20 2:58 ` John W. Linville
2006-07-20 5:22 ` Zhu Yi [this message]
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=1153372954.3485.7.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=dcbw@redhat.com \
--cc=hadi@cyberus.ca \
--cc=jketreno@linux.intel.com \
--cc=kaber@trash.net \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=stefan@loplof.de \
/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).