From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v2 7/7] net/tap: don't print pointer in info message Date: Mon, 14 Jan 2019 14:10:10 +0000 Message-ID: References: <20190111180659.5972-1-stephen@networkplumber.org> <20190111203520.19944-1-stephen@networkplumber.org> <20190111203520.19944-8-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Stephen Hemminger , keith.wiles@intel.com Return-path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 3EDB51B215 for ; Mon, 14 Jan 2019 15:10:13 +0100 (CET) In-Reply-To: <20190111203520.19944-8-stephen@networkplumber.org> Content-Language: en-US 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 1/11/2019 8:35 PM, Stephen Hemminger wrote: > Printing pointer in log is uninformative (unless in a debugger), > instead print the assigned kernel device name which correlates > well with what TAP is doing. > > Signed-off-by: Stephen Hemminger Reviewed-by: Ferruh Yigit