netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: pull request: wireless-2.6.26 2008-02-21
Date: Thu, 21 Feb 2008 12:25:25 -0500	[thread overview]
Message-ID: <20080221172525.GI3094@tuxdriver.com> (raw)
In-Reply-To: <20080221021530.GG3825-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

On Wed, Feb 20, 2008 at 09:15:30PM -0500, John W. Linville wrote:

> Here are a slew of developments intended for 2.6.26.  The patches are
> too diverse to comment upon in this summary... :-)

David,

This is additive on top of the pull request from last night.  Only
Pavel's fix for the brown-paper-bag CONFIG_MAC80211_IBSS_DEBUG build
issue is applied on top of the previous commits.

Please let me know if there are problems!

Thanks,

John

---

The following changes since commit 4d161f9d7f3f3ce069006b53dc8a84ed8a33753f:
  Johannes Berg (1):
        p54: fix sparse warnings

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git

Pavel Roskin (1):
      mac80211: fix incorrect use of CONFIG_MAC80211_IBSS_DEBUG

 net/mac80211/ieee80211_sta.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/net/mac80211/ieee80211_sta.c b/net/mac80211/ieee80211_sta.c
index 05cc908..453d14a 100644
--- a/net/mac80211/ieee80211_sta.c
+++ b/net/mac80211/ieee80211_sta.c
@@ -2452,10 +2452,12 @@ static void ieee80211_rx_bss_info(struct net_device *dev,
 		       jiffies);
 #endif /* CONFIG_MAC80211_IBSS_DEBUG */
 		if (beacon_timestamp > rx_timestamp) {
-			if (CONFIG_MAC80211_IBSS_DEBUG || net_ratelimit())
+#ifdef CONFIG_MAC80211_IBSS_DEBUG
+			if (net_ratelimit())
 				printk(KERN_DEBUG "%s: beacon TSF higher than "
 				       "local TSF - IBSS merge with BSSID %s\n",
 				       dev->name, print_mac(mac, mgmt->bssid));
+#endif /* CONFIG_MAC80211_IBSS_DEBUG */
 			ieee80211_sta_join_ibss(dev, &sdata->u.sta, bss);
 			ieee80211_ibss_add_sta(dev, NULL,
 					       mgmt->bssid, mgmt->sa);
-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org

  parent reply	other threads:[~2008-02-21 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  2:15 pull request: wireless-2.6.26 2008-02-20 John W. Linville
     [not found] ` <20080221021530.GG3825-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-02-21 17:25   ` John W. Linville [this message]
     [not found]     ` <20080221172525.GI3094-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-02-29 19:56       ` pull request: wireless-2.6.26 2008-02-21 John W. Linville
     [not found]         ` <20080229195631.GE3234-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-02-29 20:22           ` David Miller

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=20080221172525.GI3094@tuxdriver.com \
    --to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).