From: Jakub Kicinski <kuba@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Bryan Tan <bryan-bt.tan@broadcom.com>,
Vishnu Dasa <vishnu.dasa@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Simon Horman <horms@kernel.org>,
HarshaVardhana S A <harshavardhana.sa@broadcom.com>,
Bobby Eshleman <bobbyeshleman@meta.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org
Subject: Re: [PATCH] vmw_vsock: bypass false-positive Wnonnull warning with gcc-16
Date: Wed, 4 Feb 2026 18:41:16 -0800 [thread overview]
Message-ID: <20260204184116.11ec0a8c@kernel.org> (raw)
In-Reply-To: <aYMqw2HbtKi50b1e@sgarzare-redhat>
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.
next prev parent reply other threads:[~2026-02-05 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 16:34 [PATCH] vmw_vsock: bypass false-positive Wnonnull warning with gcc-16 Arnd Bergmann
2026-02-03 18:17 ` Bobby Eshleman
2026-02-04 11:29 ` Stefano Garzarella
2026-02-05 2:41 ` Jakub Kicinski [this message]
2026-02-04 14:35 ` Bryan Tan
2026-02-05 2:50 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260204184116.11ec0a8c@kernel.org \
--to=kuba@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bobbyeshleman@meta.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harshavardhana.sa@broadcom.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox