[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190716144218.20608-1-yuehaibing@huawei.com>
Date: Tue, 16 Jul 2019 22:42:18 +0800
From: YueHaibing <yuehaibing@...wei.com>
To: <kvalo@...eaurora.org>, <davem@...emloft.net>, <lkundrak@...sk>,
<derosier@...-sierra.com>
CC: <linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-wireless@...r.kernel.org>,
YueHaibing <yuehaibing@...wei.com>
Subject: [PATCH v2] libertas_tf: Use correct channel range in lbtf_geo_init
It seems we should use 'range' instead of 'priv->range'
in lbtf_geo_init(), because 'range' is the corret one
related to current regioncode.
Reported-by: Hulk Robot <hulkci@...wei.com>
Fixes: 691cdb49388b ("libertas_tf: command helper functions for libertas_tf")
Signed-off-by: YueHaibing <yuehaibing@...wei.com>
---
v2: fix compile error
---
drivers/net/wireless/marvell/libertas_tf/cmd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/marvell/libertas_tf/cmd.c b/drivers/net/wireless/marvell/libertas_tf/cmd.c
index 1eacca0..a333172 100644
--- a/drivers/net/wireless/marvell/libertas_tf/cmd.c
+++ b/drivers/net/wireless/marvell/libertas_tf/cmd.c
@@ -65,7 +65,7 @@ static void lbtf_geo_init(struct lbtf_private *priv)
break;
}
- for (ch = priv->range.start; ch < priv->range.end; ch++)
+ for (ch = range->start; ch < range->end; ch++)
priv->channels[CHAN_TO_IDX(ch)].flags = 0;
}
--
2.7.4
Powered by blists - more mailing lists