All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>,
	"Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [PATCH] lib/librte_vhost: fix bugs
Date: Tue, 10 Apr 2018 09:55:55 +0200	[thread overview]
Message-ID: <e85e18d8-55b5-020c-21ee-4b52d87cb18b@redhat.com> (raw)
In-Reply-To: <F6F2A6264E145F47A18AB6DF8E87425D7011C569@IRSMSX102.ger.corp.intel.com>



On 04/10/2018 09:47 AM, Wodkowski, PawelX wrote:
>> -----Original Message-----
>> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
>> Sent: Tuesday, April 10, 2018 9:44 AM
>> To: Wodkowski, PawelX <pawelx.wodkowski@intel.com>; Zhang, Roy Fan
>> <roy.fan.zhang@intel.com>; dev@dpdk.org
>> Cc: jianjay.zhou@huawei.com; Tan, Jianfeng <jianfeng.tan@intel.com>
>> Subject: Re: [PATCH] lib/librte_vhost: fix bugs
>>
>> Hi Pawel,
>>
>> On 04/10/2018 09:32 AM, Wodkowski, PawelX wrote:
>>>>    # all source are stored in SRCS-y
>>>>    SRCS-$(CONFIG_RTE_LIBRTE_VHOST) := fd_man.c iotlb.c socket.c vhost.c
>> \
>>>> diff --git a/lib/librte_vhost/vhost_crypto.c
>> b/lib/librte_vhost/vhost_crypto.c
>>>> index d84513e7f..2acfc908c 100644
>>>> --- a/lib/librte_vhost/vhost_crypto.c
>>>> +++ b/lib/librte_vhost/vhost_crypto.c
>>>> @@ -381,7 +381,7 @@ vhost_crypto_create_sess(struct vhost_crypto
>>>> *vcrypto,
>>>>    		return;
>>>>    	}
>>>>
>>>> -	VC_LOG_DBG("Session (key %lu, session %p) created.",
>>>> +	VC_LOG_DBG("Session (key %llu, session %p) created.",
>>>
>>> Why 'llu' instead of PRIu64 (here and there)?
>>
>> You are right, but Fan actually fixed it in updated version (the initial
>> patch has been split in 3):
>> [PATCH] vhost/crypto: fix session id printf
>>
> 
> Ohh, sorry. I need more coffee before starting review :)

No problem, that wans't obvious that these 3 patches superseded this
one.

Your reviews are welcome!
Maxime
> 
>> Cheers,
>> Maxime
>>> Pawel
>>>
> 
> Pawel
> 

      reply	other threads:[~2018-04-10  7:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 15:34 [PATCH] lib/librte_vhost: fix bugs Fan Zhang
2018-04-09 15:34 ` [PATCH] lib/librte_vhost: remove packet dump Fan Zhang
2018-04-11  8:47   ` Maxime Coquelin
2018-04-11  8:59     ` Maxime Coquelin
2018-04-11 14:36       ` Maxime Coquelin
2018-04-09 15:45 ` [PATCH] lib/librte_vhost: fix bugs Maxime Coquelin
2018-04-09 15:53 ` Maxime Coquelin
2018-04-09 16:38 ` [PATCH v2] vhost/crypto: " Fan Zhang
2018-04-09 17:57   ` [PATCH] examples/vhost_crypto: fix parsing Fan Zhang
2018-04-10  9:40     ` Maxime Coquelin
2018-04-09 18:01   ` [PATCH] vhost/crypto: fix makefile Fan Zhang
2018-04-10  9:41     ` Maxime Coquelin
2018-04-09 18:21   ` [PATCH] vhost/crypto: fix session id printf Fan Zhang
2018-04-10  9:41     ` Maxime Coquelin
2018-04-11  9:22   ` [PATCH] vhost/crypto: fix incorrect formatting Fan Zhang
2018-04-11  9:56     ` Maxime Coquelin
2018-04-10  7:32 ` [PATCH] lib/librte_vhost: fix bugs Wodkowski, PawelX
2018-04-10  7:43   ` Maxime Coquelin
2018-04-10  7:47     ` Wodkowski, PawelX
2018-04-10  7:55       ` Maxime Coquelin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e85e18d8-55b5-020c-21ee-4b52d87cb18b@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=pawelx.wodkowski@intel.com \
    --cc=roy.fan.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.