[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a9a45958-fac1-4523-96f7-19cf0b375395@lunn.ch>
Date: Thu, 11 Apr 2024 16:20:51 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
David Ahern <dsahern@...nel.org>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
nex.sw.ncis.osdt.itp.upstreaming@...el.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC net-next 7/7] netdev_features: convert
NETIF_F_FCOE_MTU to IFF_FCOE_MTU
> >> @@ -47,7 +47,6 @@ const char netdev_features_strings[NETDEV_FEATURE_COUNT][ETH_GSTRING_LEN] = {
> >>
> >> [NETIF_F_FCOE_CRC_BIT] = "tx-checksum-fcoe-crc",
> >> [NETIF_F_SCTP_CRC_BIT] = "tx-checksum-sctp",
> >> - [NETIF_F_FCOE_MTU_BIT] = "fcoe-mtu",
> >
> >
> > But this definitely _is_ a uAPI change, right?
>
> Why?
That it is not obvious why this is not a uAPI change makes it clear
this needs explaining in the commit message.
Andrew
Powered by blists - more mailing lists