netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Potnuri Bharat Teja <bharat@chelsio.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] cxgb4: Avoid -Wflex-array-member-not-at-end warning
Date: Thu, 8 Aug 2024 19:15:39 -0700	[thread overview]
Message-ID: <20240808191539.615733ab@kernel.org> (raw)
In-Reply-To: <111cc058-a681-4aec-ace4-cd6bc19699f7@embeddedor.com>

On Thu, 8 Aug 2024 12:41:32 -0600 Gustavo A. R. Silva wrote:
> >>   .../chelsio/cxgb4/cxgb4_tc_u32_parse.h        |  2 +-
> >>   include/uapi/linux/pkt_cls.h                  | 23 +++++++++++--------  
> > 
> > Took me a minute to realize you're changing uAPI.
> > Please fix the subject.  
> 
> What would be a preferred subject?

The point is that include/uapi/linux/pkt_cls.h is the more important
change.

net/sched, based on:

git log --oneline -- include/uapi/linux/pkt_cls.h

11036bd7a0b3 net/sched: cls_flower: rework TCA_FLOWER_KEY_ENC_FLAGS usage
bfda5a63137b net/sched: flower: define new tunnel flags
6e5c85c003e4 net/sched: flower: refactor control flag definitions
1d17568e74de net/sched: cls_flower: add support for matching tunnel control flags
6dd514f48110 pfcp: always set pfcp metadata
82b2545ed9a4 net/sched: Remove uapi support for tcindex classifier
41bc3e8fc1f7 net/sched: Remove uapi support for rsvp classifier
ba24ea129126 net/sched: Retire ipt action
35b1b1fd9638 Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
4c13eda757e3 tc: flower: support for SPI
4d50e50045aa net: flower: fix stack-out-of-bounds in fl_set_key_cfm()
7cfffd5fed3e net: flower: add support for matching cfm fields
1a432018c0cd net/sched: flower: Allow matching on layer 2 miss
8b189ea08c33 net/sched: flower: Add L2TPv3 filter
f86d1fbbe785 Merge tag 'net-next-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
5008750eff5d net/sched: flower: Add PPPoE filter
94dfc73e7cf4 treewide: uapi: Replace zero-length arrays with flexible-array members
b40003128226 net/sched: flower: Add number of vlan tags filter
e3acda7ade0a net/sched: Allow flower to match on GTP options

You can throw in uAPI somewhere in the subject, too

      reply	other threads:[~2024-08-09  2:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 16:24 [PATCH][next] cxgb4: Avoid -Wflex-array-member-not-at-end warning Gustavo A. R. Silva
2024-08-07 16:51 ` Simon Horman
2024-08-08  3:05 ` Jakub Kicinski
2024-08-08 18:41   ` Gustavo A. R. Silva
2024-08-09  2:15     ` Jakub Kicinski [this message]

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=20240808191539.615733ab@kernel.org \
    --to=kuba@kernel.org \
    --cc=bharat@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).