From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings Date: Tue, 21 Jun 2016 14:11:28 +0100 Message-ID: <57693D00.5090400@intel.com> References: <20160620124435.23d43f28@miho> <20160620091940.75a37c54@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: olivier.matz@6wind.com, dev@dpdk.org To: Stephen Hemminger , Simon Kagstrom Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 846F1961D for ; Tue, 21 Jun 2016 15:11:31 +0200 (CEST) In-Reply-To: <20160620091940.75a37c54@xeon-e3> 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" On 6/20/2016 5:19 PM, Stephen Hemminger wrote: > On Mon, 20 Jun 2016 12:44:35 +0200 > Simon Kagstrom wrote: > >> I.e., avoid dump messages with double 0x0x, e.g., >> >> dump mbuf at 0x0x7fac7b17c800, phys=17b17c880, buf_len=2176 >> pkt_len=2064, ol_flags=0, nb_segs=1, in_port=255 >> segment at 0x0x7fac7b17c800, data=0x0x7fac7b17c8f0, data_len=2064 >> >> Signed-off-by: Simon Kagstrom > > Agreed. Many other places have same glitch. > Hi Simon, Are you planning to extend your patch to fix all, or I can send a patch for kni and vmxnet3? Thanks, ferruh