[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240822163129.0982128f@kernel.org>
Date: Thu, 22 Aug 2024 16:31:29 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: Eric Dumazet <edumazet@...gle.com>, "David S. Miller"
<davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, David Ahern
<dsahern@...nel.org>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, Andrew Lunn
<andrew@...n.ch>, Willem de Bruijn <willemdebruijn.kernel@...il.com>,
<nex.sw.ncis.osdt.itp.upstreaming@...el.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v4 2/6] netdev_features: remove unused
__UNUSED_NETIF_F_1
On Thu, 22 Aug 2024 18:19:24 +0200 Alexander Lobakin wrote:
> > I was simply suggesting to correct the changelog, and make clear we
> > need a recent enough ethtool.
>
> Yeah I got it, thanks. Will reword.
>
> > We can not simply say that ethtool always supported the modern way
> > (ETH_SS_FEATURES)
>
> I didn't work with Linux at all back in 2011, so I didn't even know
> there were older ways of handling this :D Always something to learn, nice.
Are we removing the bit definitions just for code cleanliness?
On one hand it may be good to make any potential breakage obvious,
on the other we could avoid regressions if we stick to reserving
the bits, and reusing them, but the bits we don't delete could remain
at their current position?
Powered by blists - more mailing lists