From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Simon_K=c3=a5gstr=c3=b6m?= Subject: Re: PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings Date: Wed, 22 Jun 2016 09:08:26 +0200 Message-ID: <576A396A.8070407@netinsight.net> References: <20160620124435.23d43f28@miho> <20160620091940.75a37c54@xeon-e3> <57693D00.5090400@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: olivier.matz@6wind.com, dev@dpdk.org To: Ferruh Yigit , Stephen Hemminger Return-path: Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.21]) by dpdk.org (Postfix) with SMTP id 2FB9FB44D for ; Wed, 22 Jun 2016 09:08:32 +0200 (CEST) In-Reply-To: <57693D00.5090400@intel.com> 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 2016-06-21 15:11, Ferruh Yigit wrote: > 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. > > Are you planning to extend your patch to fix all, or I can send a patch > for kni and vmxnet3? I wasn't planning on that (this is something I just stumbled upon), so please go ahead! // Simon