[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230526211008.7b06ac3e@kernel.org>
Date: Fri, 26 May 2023 21:10:08 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, pabeni@...hat.com, davem@...emloft.net,
edumazet@...gle.com, leon@...nel.org, saeedm@...dia.com, moshe@...dia.com,
jesse.brandeburg@...el.com, anthony.l.nguyen@...el.com, tariqt@...dia.com,
idosch@...dia.com, petrm@...dia.com, simon.horman@...igine.com,
ecree.xilinx@...il.com, habetsm.xilinx@...il.com,
michal.wilczynski@...el.com, jacob.e.keller@...el.com
Subject: Re: [patch net-next v2 14/15] devlink: move port_del() to
devlink_port_ops
On Fri, 26 May 2023 12:28:40 +0200 Jiri Pirko wrote:
> Move port_del() from devlink_ops into newly introduced devlink_port_ops.
I didn't think this thru last time, I thought port_new will move
in another patch, but that's impossible (obviously?).
Isn't it kinda weird that the new callback is in one place and del
callback is in another? Asymmetric ?
Powered by blists - more mailing lists