[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260204184116.11ec0a8c@kernel.org>
Date: Wed, 4 Feb 2026 18:41:16 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: Arnd Bergmann <arnd@...nel.org>, Bryan Tan <bryan-bt.tan@...adcom.com>,
Vishnu Dasa <vishnu.dasa@...adcom.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Arnd Bergmann <arnd@...db.de>, Broadcom internal
kernel review list <bcm-kernel-feedback-list@...adcom.com>, Simon Horman
<horms@...nel.org>, HarshaVardhana S A <harshavardhana.sa@...adcom.com>,
Bobby Eshleman <bobbyeshleman@...a.com>, "Michael S. Tsirkin"
<mst@...hat.com>, linux-kernel@...r.kernel.org,
virtualization@...ts.linux.dev, netdev@...r.kernel.org
Subject: Re: [PATCH] vmw_vsock: bypass false-positive Wnonnull warning with
gcc-16
On Wed, 4 Feb 2026 12:29:44 +0100 Stefano Garzarella wrote:
> Not sure if it's net or net-next material, maybe net to avoid the
> warning/error on v6.19 too ?
I think net-next. I assume people who build with werror like pain,
and we need to be inclusive.
Powered by blists - more mailing lists