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 <simon.kagstrom at netinsight.net> 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 <simon.kagstrom at netinsight.net> >> >> 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
