From: Pavel Fedin <p.fedin@samsung.com>
To: "'Xie, Huawei'" <huawei.xie@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [RESEND PATCH] vhost_user: Make sure that memory map is set before attempting address translation
Date: Fri, 15 Jan 2016 11:10:24 +0300 [thread overview]
Message-ID: <000001d14f6c$2ffe43f0$8ffacbd0$@samsung.com> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B4C589C81@SHSMSX101.ccr.corp.intel.com>
Hello!
> If this is the case, i am wondering whether we should include
> "malfunctioning clients" in commit message. It triggers me to think if
> there are existing buggy implementations.
Well... Can you suggest how to rephrase it? May be "if a client is malfunctioning it can..."? I lack fantasy, really, and to tell
the truth i don't care that much about the exact phrasing, i'm OK with everything.
> Anyway, check is OK.
Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2016-01-15 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 7:32 Pavel Fedin
2016-01-13 9:24 ` Xie, Huawei
2016-01-13 9:40 ` Pavel Fedin
2016-01-13 12:48 ` Xie, Huawei
2016-01-15 8:10 ` Pavel Fedin [this message]
2016-01-18 17:29 ` Xie, Huawei
2016-02-21 9:54 ` Thomas Monjalon
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='000001d14f6c$2ffe43f0$8ffacbd0$@samsung.com' \
--to=p.fedin@samsung.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).