From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id 4716A152A for ; Mon, 9 Jan 2017 18:03:37 +0100 (CET) Received: by mail-pf0-f179.google.com with SMTP id f144so22584960pfa.2 for ; Mon, 09 Jan 2017 09:03:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=3oe1BbDeZUJl4c6dA5FvzcIS9jNfxslBHmPOFmijh18=; b=gNHJrchgXCCZPMXMvzSFGpA4xuHdf0bubyAnhTiFOJoiafMmb7bgQ6tLV9yNS0YXYe 1lfLiBjbk7q7W3Kftc9memqNaTz4FSkL5qF3NVZxF5wIGnKLCivl0uPTXPxMAsKozEdS qJu5GN66BhFlFdaFwVc2xd+eLzqLhEQAuQ/VFFhPvFaR93dx5jTt8cgWWBvwI4A+Qj7f GFJ+TpYKQXQhk5aWqhdIe8RBdWgsrd214w2vhGqtYimERBop7XnAT6ov7iSXEjRuYrxg +4hbwho3ANBM1F4JtdoZuEWjVVw6/2hJ+AJ5oiFyIJPOgKHX3cY6lNsLT+LsNZZ8NUvi nPZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=3oe1BbDeZUJl4c6dA5FvzcIS9jNfxslBHmPOFmijh18=; b=iFzK3DUfEtBtLfnpCikMOXOz6mKcLdvIICmRG53Vbt+f/qwLCTz/oWzwxJ0v/dvVn+ GY9Bznl7ueEyeLUttP+JH4zOnU0nQ4ZSqmnqsZV5vpFdSbmqMYsj1EtKQbmQ71fuy946 /25ogY3dOtSZKDkVPBUZkdcSHf2edAKmOxchSApr42k/O+7KNzpjeAqTO7snWFSvfCq0 q2riYpNyw10iE7UJCYCZok/XzLnBipVlwPCNFHdgKKvMXtYyD+HVd/t/j8ZJZ9oOkJzv koI76oYQiBpp836SK95MjsCQbTOhSxAtRr6La2gsW0NipniepckOT8AetDs6K2i1esXD XEtA== X-Gm-Message-State: AIkVDXLu2n1kcAJ6OxcQABX3g+7Uocvw2DRwgYIiII4r1PIbpPI/BPFN+Oa4g+0BOETACQ== X-Received: by 10.84.140.3 with SMTP id 3mr194743217pls.61.1483981416456; Mon, 09 Jan 2017 09:03:36 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id z77sm808832pfk.47.2017.01.09.09.03.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 09 Jan 2017 09:03:36 -0800 (PST) Date: Mon, 9 Jan 2017 09:03:28 -0800 From: Stephen Hemminger To: Ajit Khaparde Cc: dev@dpdk.org Message-ID: <20170109090328.4768b23f@xeon-e3> In-Reply-To: <20170106195517.52821-1-ajit.khaparde@broadcom.com> References: <20170106195517.52821-1-ajit.khaparde@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] net/bnxt: Add support for new PCI IDs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 17:03:37 -0000 fine BROADCOM_DEV_ID_57416_MF 0x16ee > > static struct rte_pci_id bnxt_pci_id_map[] = { > { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57301) }, > @@ -95,6 +110,21 @@ static struct rte_pci_id bnxt_pci_id_map[] = { > { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57407_MF) }, Adding new id's is good. Does this now cover all the devices in the Linux kernel? The PCI id table should be const?