From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v6 05/17] eal: introduce init macros Date: Fri, 15 Jul 2016 14:38:28 +0200 Message-ID: <1886837.lFmbahJrCS@xps13> References: <1466510566-9240-1-git-send-email-shreyansh.jain@nxp.com> <20160714175707.43755987@jvn> <5788BF88.3060607@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, david.marchand@6wind.com To: Shreyansh jain , Jan Viktorin Return-path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id 6240D47D1 for ; Fri, 15 Jul 2016 14:38:31 +0200 (CEST) Received: by mail-wm0-f54.google.com with SMTP id i5so28111826wmg.0 for ; Fri, 15 Jul 2016 05:38:31 -0700 (PDT) In-Reply-To: <5788BF88.3060607@nxp.com> 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" Hi guys, 2016-07-15 16:18, Shreyansh jain: > On Thursday 14 July 2016 09:27 PM, Jan Viktorin wrote: > > Please. The time is almost gone. 18/7/2016 is the release (according > > to the roadmap)... I have to fix it in my patchset, otherwise it > > does not build (after moving the .name from rte_pci_driver to > > rte_driver). > > I didn't consider 18/Jul. > Please go ahead. I will continue to send v7 _without_ the above change > so that your patchset doesn't break. This way you will not get blocked > because of me. [...] > > I'd like to preserve the clear semantics. That is DRIVER_REGISTER_PCI > > -> give a pci device. > > > > Has anybody a different opinion? David? Thomas? > > Yes please. > Or else, if nothing comes up soon, I will simply go ahead and change to > DRIVER_REGISTER_PCI(eth_driver.pci_drv) as this trivial issue shouldn't > hold back this series. I'm sorry I have no time to review these series shortly. I think it is too late to consider an integration in 16.07 unfortunately. I feel you are doing a great job and we can target to have these changes in the early days of 16.11 (in August). As this is a big refactoring, it is probably a good idea to integrate it in the beginning of the next release integration cycle.