From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 681BF379E for ; Wed, 13 Jan 2016 13:22:33 +0100 (CET) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id BB800C0A848C; Wed, 13 Jan 2016 12:22:32 +0000 (UTC) Received: from sopuli.koti.laiskiainen.org (vpn1-7-206.ams2.redhat.com [10.36.7.206]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u0DCMV2S028199; Wed, 13 Jan 2016 07:22:31 -0500 To: Bruce Richardson , Stephen Hemminger References: <1451357606-117892-1-git-send-email-ziye.yang@intel.com> <20151231091214.0acd9d4e@xeon-e3> <20160113115503.GC7216@bricha3-MOBL3> From: Panu Matilainen Message-ID: <56964186.1060800@redhat.com> Date: Wed, 13 Jan 2016 14:22:30 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160113115503.GC7216@bricha3-MOBL3> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 Cc: Ziye Yang , dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] pci: Add the class_id support in pci probe X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 12:22:33 -0000 On 01/13/2016 01:55 PM, Bruce Richardson wrote: > 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? There might not be applications using it but drivers are ABI consumers too - think of 3rd party drivers and such. - Panu -