From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH] pci: Add the class_id support in pci probe Date: Wed, 13 Jan 2016 11:55:03 +0000 Message-ID: <20160113115503.GC7216@bricha3-MOBL3> References: <1451357606-117892-1-git-send-email-ziye.yang@intel.com> <20151231091214.0acd9d4e@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ziye Yang , dev@dpdk.org To: Stephen Hemminger Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 4D1188DAD for ; Wed, 13 Jan 2016 12:55:09 +0100 (CET) Content-Disposition: inline In-Reply-To: <20151231091214.0acd9d4e@xeon-e3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Dec 31, 2015 at 09:12:14AM -0800, Stephen Hemminger wrote: > On Tue, 29 Dec 2015 10:53:26 +0800 > Ziye Yang wrote: > > > This patch is used to add the class_id support > > for pci_probe since some devices need the class_info > > (class_code, subclass_code, programming_interface) > > > > Signed-off-by: Ziye Yang > > Since rte_pci is exposed to application this breaks the ABI. But applications are not going to be defining rte_pci_ids values internally, are they? That is for drivers to use. Is this really an ABI breakage for applications that we need to be concerned about? /Bruce