From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Blunck Subject: Re: [PATCH v5 20/20] ethdev: Decouple from PCI device Date: Fri, 23 Dec 2016 17:20:39 +0100 Message-ID: References: <1482508691-11408-1-git-send-email-jblunck@infradead.org> <1482508691-11408-21-git-send-email-jblunck@infradead.org> <2185678.prfkkk662h@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: dev@dpdk.org, Shreyansh Jain , David Marchand , Stephen Hemminger To: Thomas Monjalon Return-path: Received: from mail-wm0-f66.google.com (mail-wm0-f66.google.com [74.125.82.66]) by dpdk.org (Postfix) with ESMTP id 2BB932B9F for ; Fri, 23 Dec 2016 17:20:40 +0100 (CET) Received: by mail-wm0-f66.google.com with SMTP id m203so42298719wma.3 for ; Fri, 23 Dec 2016 08:20:40 -0800 (PST) In-Reply-To: <2185678.prfkkk662h@xps13> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Dec 23, 2016 at 5:17 PM, Thomas Monjalon wrote: > 2016-12-23 16:58, Jan Blunck: >> +/** >> + * @internal >> + * Helper macro for drivers that need to convert to struct rte_pci_device. >> + */ >> +#define RTE_DEV_PCI_DEV(ptr) container_of(ptr, struct rte_pci_device, device) > > Do you prefer to rename to RTE_DEV_TO_PCI? I'm fine with that. > >> + struct rte_device *device; /**< Backing device for this device */ > > This comment looks strange. > shorten to just "Backing device"? Agreed.