[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877cc2ujef.fsf@kernel.org>
Date: Tue, 27 Aug 2024 17:31:36 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Hongbo Li <lihongbo22@...wei.com>, <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
Jakub Kicinski <kuba@...nel.org> writes:
> On Tue, 27 Aug 2024 07:45:02 +0300 Kalle Valo wrote:
>> > Do you mean some patches will go to other branches (such as mac80211)?
>>
>> Jakub means that your patchset had compilation errors, see the red on
>> patchwork:
>>
>> https://patchwork.kernel.org/project/netdevbpf/list/?series=882901&state=*&order=date
>
> FWIW I prefer not to point noobs to the patchwork checks, lest they
> think it's a public CI and they can fling broken code at the list :(
Good point, that's definitely what we do not want. I'll keep this in
mind.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
https://docs.kernel.org/process/submitting-patches.html
Powered by blists - more mailing lists