[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a92bb68-7fe7-4bf2-885f-e07b06ea82aa@huawei.com>
Date: Tue, 27 Aug 2024 10:57:06 +0800
From: Hongbo Li <lihongbo22@...wei.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <johannes@...solutions.net>, <davem@...emloft.net>, <edumazet@...gle.com>,
<pabeni@...hat.com>, <allison.henderson@...cle.com>, <dsahern@...nel.org>,
<pshelar@....org>, <linux-wireless@...r.kernel.org>,
<netdev@...r.kernel.org>, <rds-devel@....oracle.com>, <dccp@...r.kernel.org>,
<dev@...nvswitch.org>, <linux-afs@...ts.infradead.org>
Subject: Re: [PATCH net-next 0/8] Use max/min to simplify the code
On 2024/8/27 5:44, Jakub Kicinski wrote:
> On Sat, 24 Aug 2024 15:40:25 +0800 Hongbo Li wrote:
>> Many Coccinelle/coccicheck warning reported by minmax.cocci
>> in net module, such as:
>> WARNING opportunity for max()
>> WARNING opportunity for min()
>>
>> Let's use max/min to simplify the code and fix these warnings.
>> These patch have passed compilation test.
>
> This set does not build.
>
Do you mean some patches will go to other branches (such as mac80211)?
Thanks,
Hongbo
>
Powered by blists - more mailing lists