From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arybchenko@solarflare.com>
Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com
 [148.163.129.52]) by dpdk.org (Postfix) with ESMTP id 9DC317CDC
 for <dev@dpdk.org>; Mon,  9 Jul 2018 10:16:42 +0200 (CEST)
X-Virus-Scanned: Proofpoint Essentials engine
Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1-us4.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id
 165444C005C; Mon,  9 Jul 2018 08:16:41 +0000 (UTC)
Received: from [192.168.1.16] (85.187.13.33) by ukex01.SolarFlarecom.com
 (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Mon, 9 Jul
 2018 09:16:30 +0100
To: Jeff Guo <jia.guo@intel.com>, <stephen@networkplumber.org>,
 <bruce.richardson@intel.com>, <ferruh.yigit@intel.com>,
 <konstantin.ananyev@intel.com>, <gaetan.rivet@6wind.com>,
 <jingjing.wu@intel.com>, <thomas@monjalon.net>, <motih@mellanox.com>,
 <matan@mellanox.com>, <harry.van.haaren@intel.com>, <qi.z.zhang@intel.com>,
 <shaopeng.he@intel.com>, <bernard.iremonger@intel.com>
CC: <jblunck@infradead.org>, <shreyansh.jain@nxp.com>, <dev@dpdk.org>,
 <helin.zhang@intel.com>
References: <1530787185-5915-1-git-send-email-jia.guo@intel.com>
 <1531119413-17298-1-git-send-email-jia.guo@intel.com>
 <1531119413-17298-4-git-send-email-jia.guo@intel.com>
From: Andrew Rybchenko <arybchenko@solarflare.com>
Message-ID: <e4d9659d-95e1-8681-f51b-2b7039a33276@solarflare.com>
Date: Mon, 9 Jul 2018 11:16:23 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <1531119413-17298-4-git-send-email-jia.guo@intel.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: [85.187.13.33]
X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To
 ukex01.SolarFlarecom.com (10.17.10.4)
X-TM-AS-Product-Ver: SMEX-11.0.0.1191-8.100.1062-23956.003
X-TM-AS-Result: No--2.597300-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
X-MDID: 1531124202-RQh_ojEhRJ5z
Subject: Re: [dpdk-dev] [PATCH v2 3/3] testpmd: remove the dev event
	callback register
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2018 08:16:42 -0000

On 09.07.2018 09:56, Jeff Guo wrote:
> Since now we can use driver to management the eal event for hotplug,
> so no need to register dev event callback in app anymore. This patch
> remove the related code.

I don't understand why handling on device level means removal
of the application callback. May be as a cleanup.
I guess application still could be interested in device addition and
removal events. It is mainly question to testpmd maintainer.