lkml.org 
[lkml]   [2020]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH AUTOSEL 4.14 251/371] libertas_tf: Use correct channel range in lbtf_geo_init
    Date
    From: YueHaibing <yuehaibing@huawei.com>

    [ 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: 691cdb49388b ("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>
    ---
    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 909ac3685010..2b193f1257a5 100644
    --- a/drivers/net/wireless/marvell/libertas_tf/cmd.c
    +++ b/drivers/net/wireless/marvell/libertas_tf/cmd.c
    @@ -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;
    }

    --
    2.20.1
    \
     
     \ /
      Last update: 2020-01-16 19:20    [W:4.725 / U:1.432 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site