From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Rich Lane <rich.lane@bigswitch.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: remove vhost_net_device_ops
Date: Mon, 15 Feb 2016 13:57:06 +0800 [thread overview]
Message-ID: <20160215055706.GA21426@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1455132428-46926-1-git-send-email-rlane@bigswitch.com>
On Wed, Feb 10, 2016 at 11:27:08AM -0800, Rich Lane wrote:
> The indirection is unnecessary because there is only one implementation of the
> vhost common code. Removing it makes the code more readable.
This is a good cleanup! A minor nit is that I saw few long lines
exceeding 80 chars.
--yliu
next prev parent reply other threads:[~2016-02-15 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 19:27 Rich Lane
2016-02-15 5:57 ` Yuanhan Liu [this message]
2016-02-16 22:45 ` [dpdk-dev] [PATCH v2] " Rich Lane
2016-02-17 12:58 ` Yuanhan Liu
2016-02-19 15:12 ` Thomas Monjalon
2016-02-19 18:10 ` [dpdk-dev] [PATCH v3] " Rich Lane
2016-02-19 18:34 ` 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=20160215055706.GA21426@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=rich.lane@bigswitch.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).