[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201026065235.GG18329@kadam>
Date: Mon, 26 Oct 2020 09:52:36 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Yunsheng Lin <linyunsheng@...wei.com>
Cc: Yisen Zhuang <yisen.zhuang@...wei.com>,
Salil Mehta <salil.mehta@...wei.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Huazhong Tan <tanhuazhong@...wei.com>,
Yonglong Liu <liuyonglong@...wei.com>,
Yufeng Mo <moyufeng@...wei.com>,
Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@...el.com>,
Guangbin Huang <huangguangbin2@...wei.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH net] net: hns3: clean up a return in hclge_tm_bp_setup()
On Mon, Oct 26, 2020 at 11:18:16AM +0800, Yunsheng Lin wrote:
> On 2020/10/23 19:22, Dan Carpenter wrote:
> > Smatch complains that "ret" might be uninitialized if we don't enter
> > the loop. We do always enter the loop so it's a false positive, but
> > it's cleaner to just return a literal zero and that silences the
> > warning as well.
>
> Thanks for the clean up. Minor comment below:
> Perhap it makes sense to limit ret scope within the for loop after
> returning zero.
>
It's not really normal to limit ret scope... I think it's better to
leave it as-is.
regards,
dan carpenter
Powered by blists - more mailing lists