From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: PATCH] mbuf: rte_pktmbuf_dump: don't add 0x when
 using %p in format strings
Date: Thu, 23 Jun 2016 11:58:19 +0100
Message-ID: <576BC0CB.6010507@intel.com>
References: <20160620124435.23d43f28@miho> <20160620091940.75a37c54@xeon-e3>
 <57693D00.5090400@intel.com> <576A396A.8070407@netinsight.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: olivier.matz@6wind.com, dev@dpdk.org
To: =?UTF-8?Q?Simon_K=c3=a5gstr=c3=b6m?= <simon.kagstrom@netinsight.net>,
 Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mga03.intel.com (mga03.intel.com [134.134.136.65])
 by dpdk.org (Postfix) with ESMTP id EAC8195EC
 for <dev@dpdk.org>; Thu, 23 Jun 2016 12:58:21 +0200 (CEST)
In-Reply-To: <576A396A.8070407@netinsight.net>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 6/22/2016 8:08 AM, Simon K=E5gstr=F6m 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 <simon.kagstrom@netinsight.net> wrote:
>>>
>>>> I.e., avoid dump messages with double 0x0x, e.g.,
>>>>
>>>>   dump mbuf at 0x0x7fac7b17c800, phys=3D17b17c880, buf_len=3D2176
>>>>     pkt_len=3D2064, ol_flags=3D0, nb_segs=3D1, in_port=3D255
>>>>     segment at 0x0x7fac7b17c800, data=3D0x0x7fac7b17c8f0, data_len=3D=
2064
>>>>
>>>> Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
>>>
>>> Agreed. Many other places have same glitch.
>>
>> Are you planning to extend your patch to fix all, or I can send a patc=
h
>> for kni and vmxnet3?
>=20
> I wasn't planning on that (this is something I just stumbled upon), so
> please go ahead!
>=20

For KNI, 0x%p is valid usage for printk(), so only sending patch for
vmxnet3.

Thanks,
ferruh