From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 7CAEB4CB3 for ; Tue, 8 May 2018 22:18:28 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2792821215; Tue, 8 May 2018 16:18:28 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 08 May 2018 16:18:28 -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=9WU+Rv9maGbzr2s1C+ZeP3JZGt fDACANfKEsoDAlb4o=; b=IuibnS9XCTckU8r2J/W9Cm/M+6WCMNvWnHKg8MjRiX hVjSn4xga+OIDe8vNxiAXocc3BjpcNUIN5tgV1L8680RUYUbpppqjzQDorK1OvzH Umzimxpvze6LVFjSrXzaTzWNbAJv8ZVcze4Jljc7wrxiR2pAe3ewEP1irdt1HLnf U= 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=fm2; bh=9WU+Rv 9maGbzr2s1C+ZeP3JZGtfDACANfKEsoDAlb4o=; b=A4i0Q4E0gjVG1VSx0VMWkR 8Z8rZQrrm5Mmfv8k52wpeegFR7r3Wd+jjXbySLAUwO60x9dxRYHpxwtMIgspKlU2 afBE7b1YCb9DU1zGh/fkunrY2vqOMZvpFFR28qv97RRohbeXvuh/Q3cKheXoxCan 79XiXC1wlEl4YC2FVYs8Px4jurfROtUR6RzJvBRvgb+NItVlhc8cawQBerJz3Vg+ zAPpCIiCFOuxbwERS9tl++kWZ69+iraydr/FHPs4R/EsU3itn9Xej+0HqQL6OQAK VgfvYy66jt5KPeMR5hlhjG7KHKhUMbO2NyShIacs+wHaGKxkH9jTtQ6qL7PvB8lg == 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 4649DE509B; Tue, 8 May 2018 16:18:27 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, Maxime Coquelin , Hemant Agrawal , Shreyansh Jain Date: Tue, 08 May 2018 22:18:25 +0200 Message-ID: <5069880.AX8dYsygPy@xps> In-Reply-To: <8708c256-8154-9552-1442-3f6a7baea6d1@redhat.com> References: <0016ba7532becb9168ec1f53bf578fffa2bd206b.1525333611.git.anatoly.burakov@intel.com> <8708c256-8154-9552-1442-3f6a7baea6d1@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 18.05-RC3 v2] mem: add argument to mem event callbacks 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: Tue, 08 May 2018 20:18:28 -0000 04/05/2018 09:35, Maxime Coquelin: > Hi Anatoly, > > On 05/03/2018 10:28 AM, Anatoly Burakov wrote: > > It may be useful to pass arbitrary data to the callback (such > > as device pointers), so add this to the mem event callback API. > > > > Signed-off-by: Anatoly Burakov > > Suggested-by: Maxime Coquelin > > Thanks for doing this change, FWIW: > Tested-by: Maxime Coquelin > Acked-by: Maxime Coquelin Applied, thanks