From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"stable@kernel.org" <stable@kernel.org>,
John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: [PATCH] ath9k: remove duplicate set_frag_threshold
Date: Tue, 28 Oct 2008 12:41:37 -0700 [thread overview]
Message-ID: <20081028194137.GG8463@tesla> (raw)
In-Reply-To: <43e72e890810281201n6e119153k959283ced1abb757@mail.gmail.com>
This removes a duplicate set_frag_threshold which was overlooked.
The last set_frag_threshold simply overwrites the pointer for
set_rts_threshold so no harm is currently done.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Luis R. Rodriguez" <lrodriguez@atheros.com>
---
Feel free to ignore this patch for stable as I see no issue
with the current behaviour which would cause an oops.
--- a/drivers/net/wireless/ath9k/main.c.orig 2008-10-28 11:55:49.000000000 -0700
+++ b/drivers/net/wireless/ath9k/main.c 2008-10-28 11:56:00.000000000 -0700
@@ -1031,7 +1031,6 @@
.hw_scan = NULL,
.get_tkip_seq = NULL,
.set_rts_threshold = NULL,
- .set_frag_threshold = NULL,
.set_retry_limit = NULL,
.get_tsf = ath9k_get_tsf,
.reset_tsf = ath9k_reset_tsf,
prev parent reply other threads:[~2008-10-28 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1225209597.3598.18.camel@johannes.berg>
2008-10-28 19:01 ` [PATCH] ath9k: remove useless NULL initialisers Luis R. Rodriguez
2008-10-28 19:41 ` Luis R. Rodriguez [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=20081028194137.GG8463@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.