From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v1 net-next 1/4] selftest: af_unix: Add -Wall and -Wflex-array-member-not-at-end to CFLAGS.
Date: Tue, 12 Aug 2025 18:02:56 -0700 [thread overview]
Message-ID: <20250812180256.712d316b@kernel.org> (raw)
In-Reply-To: <20250811215432.3379570-2-kuniyu@google.com>
On Mon, 11 Aug 2025 21:53:04 +0000 Kuniyuki Iwashima wrote:
> -Wall and -Wflex-array-member-not-at-end caught some warnings that
> will be fixed in later patches.
Makes sense to enable the warnings first when writing the patches,
but I think we should commit in the opposite order. Fixes fix then
arm the warnings. I'll reorder when applying.
next prev parent reply other threads:[~2025-08-13 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 21:53 [PATCH v1 net-next 0/4] selftest: af_unix: Enable -Wall and -Wflex-array-member-not-at-end Kuniyuki Iwashima
2025-08-11 21:53 ` [PATCH v1 net-next 1/4] selftest: af_unix: Add -Wall and -Wflex-array-member-not-at-end to CFLAGS Kuniyuki Iwashima
2025-08-13 1:02 ` Jakub Kicinski [this message]
2025-08-13 5:33 ` Kuniyuki Iwashima
2025-08-11 21:53 ` [PATCH v1 net-next 2/4] selftest: af_unix: Silence -Wflex-array-member-not-at-end warning for scm_inq.c Kuniyuki Iwashima
2025-08-11 21:53 ` [PATCH v1 net-next 3/4] selftest: af_unix: Silence -Wflex-array-member-not-at-end warning for scm_rights.c Kuniyuki Iwashima
2025-08-11 21:53 ` [PATCH v1 net-next 4/4] selftest: af_unix: Silence -Wall warning for scm_pid.c Kuniyuki Iwashima
2025-08-13 1:10 ` [PATCH v1 net-next 0/4] selftest: af_unix: Enable -Wall and -Wflex-array-member-not-at-end 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=20250812180256.712d316b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.