[dpdk-dev] PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings

2016-06-24 Thread Thomas Monjalon
2016-06-20 12:44, Simon Kagstrom: > 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 > >

[dpdk-dev] PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings

2016-06-23 Thread Ferruh Yigit
On 6/22/2016 8:08 AM, Simon K?gstr?m wrote: > 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

[dpdk-dev] PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings

2016-06-22 Thread Simon Kågström
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 >>>

[dpdk-dev] PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings

2016-06-20 Thread Simon Kagstrom
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 ---

[dpdk-dev] PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when using %p in format strings

2016-06-20 Thread Stephen Hemminger
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,