From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 0A39F1B465 for ; Thu, 27 Sep 2018 14:40:36 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E307F21D34; Thu, 27 Sep 2018 08:40:34 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 27 Sep 2018 08:40:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=d9L2zSpu01i0+DCNKVEt31HVIp utao5q79mThBj0N+Y=; b=Luc2xYPM8buFlCosJ012mmBp9Wz9N0VXvwmxjViI9y IvA0imAmXgeJ9+i/QW4XGqlD9dJ2iFKHVOc6Sk+txYsiphobvMROuEYrj+IbGG0U CmNBxj+OYW49qP3gy8kWmZNURjiN4h+v0VOCnaqurkEviGZjp4bZsw3Y9ZScfp3g c= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=d9L2zS pu01i0+DCNKVEt31HVIputao5q79mThBj0N+Y=; b=hXBBE3ApTd+mZ93ISM2QXM 9TpcbTmwu+lLfkV8mwMPyiw331UfS+CBeTYtuM2l9YvebNxVFTGwj1lUhBB5d80T b7sEXpF26cUZoWOm3fpHKF31d6RGqManqIuexRWV4SAHJmx6xjRYhsaypQzBDIeZ hyZmjsRDNN3XdhgPTD1ri5v75V9R0j4rR09TNiZMXnSI9l4lkYlM0oY9ywGMHHC7 66osh8+kX77liZWw90KyDXHwfcEtZaTvte1jeXEIJTtxYVNihNfVq8s3jUSH0wg5 VX5ItVBjnMJ9OPTOTVUAWowxxD28gDc6sXmJazpYiknnEmMNMFAVO1EsdElb/w0A == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C6990102E0; Thu, 27 Sep 2018 08:40:33 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, hemant.agrawal@nxp.com Date: Thu, 27 Sep 2018 14:40:32 +0200 Message-ID: <2039580.JQpZYNxiQt@xps> In-Reply-To: References: <20180925192259.12249-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] drivers/bus: fill driver reference after NXP probing 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: Thu, 27 Sep 2018 12:40:36 -0000 26/09/2018 10:12, Shreyansh Jain: > On Wednesday 26 September 2018 12:52 AM, Thomas Monjalon wrote: > > The probing functions of NXP buses were missing to set > > the driver used for successfully probing a device. > > > > The NXP driver and the generic rte_driver are now set > > in the device structures. > > > > Signed-off-by: Thomas Monjalon > > --- > > A part of this was already being done in the drv->probe(), though it was > not complete (dpaa2_dev->driver = dpaa2_drv; was not being done). > > --->8---net/dpaa2/dpaa2_ethdev.c-- > 2008 > 2009 eth_dev->device = &dpaa2_dev->device; > 2010 eth_dev->device->driver = &dpaa2_drv->driver; > 2011 > --->8--- I guess we could remove the driver assignment in NXP drivers, after this patch applied. > Thank you! > > Acked-by: Shreyansh Jain Applied