From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Kicinski Subject: Re: [RFC iproute2-next] devlink: add info subcommand Date: Tue, 15 Jan 2019 09:58:15 -0800 Message-ID: <20190115095815.128eeb84@cakuba.netronome.com> References: <20190115005009.16025-1-jakub.kicinski@netronome.com> <20190115005009.16025-8-jakub.kicinski@netronome.com> <20190115082011.GB2290@nanopsycho> <20190115140046.GG19687@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Jiri Pirko , davem@davemloft.net, netdev@vger.kernel.org, oss-drivers@netronome.com To: Andrew Lunn Return-path: Received: from mail-qk1-f193.google.com ([209.85.222.193]:34176 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727667AbfAOR6U (ORCPT ); Tue, 15 Jan 2019 12:58:20 -0500 Received: by mail-qk1-f193.google.com with SMTP id q8so2113538qke.1 for ; Tue, 15 Jan 2019 09:58:19 -0800 (PST) In-Reply-To: <20190115140046.GG19687@lunn.ch> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 15 Jan 2019 15:00:46 +0100, Andrew Lunn wrote: > I could have a line card implementing a port which has version > information, as well as version information for the backplane which > would be under dev. I'd argue a line card is not a port, so adding port info for line cards is, again, taking a step backward towards unclear semantics. Line cards are a very well understood concept, and they deserve their own handling. And ports may _belong_ to line cards.