linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Sujith Manoharan <Sujith.Manoharan@atheros.com>
Subject: [PATCH] ath9k: remove fragmentation workaround again
Date: Tue, 09 Dec 2008 12:26:14 +0100	[thread overview]
Message-ID: <1228821974.22164.201.camel@johannes.berg> (raw)

Looking at the RC algorithm this is no longer necessary.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
Untested, but the error that used to happen will no longer happen since
now the sub-structure is assigned by the driver, in rate_driver_data,
per fragment.

 drivers/net/wireless/ath9k/main.c |    6 ------
 1 file changed, 6 deletions(-)

--- everything.orig/drivers/net/wireless/ath9k/main.c	2008-12-08 21:54:08.000000000 +0100
+++ everything/drivers/net/wireless/ath9k/main.c	2008-12-08 21:54:20.000000000 +0100
@@ -2423,11 +2423,6 @@ static int ath9k_ampdu_action(struct iee
 	return ret;
 }
 
-static int ath9k_no_fragmentation(struct ieee80211_hw *hw, u32 value)
-{
-	return -EOPNOTSUPP;
-}
-
 static struct ieee80211_ops ath9k_ops = {
 	.tx 		    = ath9k_tx,
 	.start 		    = ath9k_start,
@@ -2444,7 +2439,6 @@ static struct ieee80211_ops ath9k_ops = 
 	.get_tsf 	    = ath9k_get_tsf,
 	.reset_tsf 	    = ath9k_reset_tsf,
 	.ampdu_action       = ath9k_ampdu_action,
-	.set_frag_threshold = ath9k_no_fragmentation,
 };
 
 static struct {



             reply	other threads:[~2008-12-09 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 11:26 Johannes Berg [this message]
2008-12-09 16:39 ` [PATCH] ath9k: remove fragmentation workaround again Jouni Malinen
2008-12-09 16:51   ` Johannes Berg

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=1228821974.22164.201.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).