[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220608202934.6412b843@kernel.org>
Date: Wed, 8 Jun 2022 20:29:34 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: David Ahern <dsahern@...nel.org>
Cc: Jiri Pirko <jiri@...nulli.us>, davem@...emloft.net,
netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com,
steffen.klassert@...unet.com, jreuter@...na.de,
razor@...ckwall.org, kgraul@...ux.ibm.com, ivecera@...hat.com,
jmaloy@...hat.com, ying.xue@...driver.com, lucien.xin@...il.com,
arnd@...db.de, yajun.deng@...ux.dev, atenart@...nel.org,
richardsonnick@...gle.com, hkallweit1@...il.com,
linux-hams@...r.kernel.org, dev@...nvswitch.org,
linux-s390@...r.kernel.org, tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next] net: rename reference+tracking helpers
On Wed, 8 Jun 2022 16:58:08 -0600 David Ahern wrote:
> On 6/8/22 8:58 AM, Jakub Kicinski wrote:
> > IMO to encourage use of the track-capable API we could keep their names
> > short and call the legacy functions __netdev_hold() as I mentioned or
> > maybe netdev_hold_notrack().
>
> I like that option. Similar to the old nla_parse functions that were
> renamed with _deprecated - makes it easier to catch new uses.
Well, not really a perfect parallel because _deprecated nla has to stay
forever, given it behaves differently, while _notrack would hopefully
die either thru conversion or someone rightly taking an axe to the
cobwebbed code.
Either way, I hope nobody is against merging the current patch.
Powered by blists - more mailing lists