From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xie, Huawei" <huawei.xie@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] lib/librte_vhost: exchange kickfd and callfd to avoid confusion
Date: Mon, 09 Mar 2015 09:33:48 +0100 [thread overview]
Message-ID: <3469946.QfMTY0AsFA@xps13> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F962511A0F456@shsmsx102.ccr.corp.intel.com>
> > Previous vhost implementation wrongly name kickfd as callfd and callfd as
> > kickfd.
> > It is functional correct, but causes confusion.
> >
> > Signed-off-by: Huawei Xie <huawei.xie@intel.com>
>
> Acked-by: Changchun Ouyang <changchun.ouyang@intel.com>
Applied, thanks
next prev parent reply other threads:[~2015-03-09 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 10:39 Huawei Xie
2015-03-06 11:05 ` [dpdk-dev] [PATCH] test whether file descriptor is valid before close it Huawei Xie
2015-03-09 1:32 ` Ouyang, Changchun
2015-03-09 8:34 ` Thomas Monjalon
2015-03-09 2:23 ` Tetsuya Mukawa
2015-03-09 1:28 ` [dpdk-dev] [PATCH] lib/librte_vhost: exchange kickfd and callfd to avoid confusion Ouyang, Changchun
2015-03-09 8:33 ` Thomas Monjalon [this message]
2015-03-09 2:23 ` Tetsuya Mukawa
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=3469946.QfMTY0AsFA@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).