libertas_tf: Use correct channel range in lbtf_geo_init
[ Upstream commit 2ec4ad49b98e4a14147d04f914717135eca7c8b1 ]
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@huawei.com>
Fixes: 691cdb4938
("libertas_tf: command helper functions for libertas_tf")
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
9311fd211a
commit
81e26cee53
1 changed files with 1 additions and 1 deletions
|
@ -69,7 +69,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;
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue