From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 3/3] vhost: update comments
Date: Fri, 4 Nov 2016 22:15:18 +0800 [thread overview]
Message-ID: <20161104141518.GA12283@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20264A8CB@IRSMSX103.ger.corp.intel.com>
On Fri, Nov 04, 2016 at 01:28:45PM +0000, Mcnamara, John wrote:
>
>
> > -----Original Message-----
> > From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> > Sent: Wednesday, November 2, 2016 3:15 AM
> > To: dev@dpdk.org
> > Cc: Mcnamara, John <john.mcnamara@intel.com>; Yuanhan Liu
> > <yuanhan.liu@linux.intel.com>
> > Subject: [PATCH 3/3] vhost: update comments
> >
> > vhost-cuse is removed, update corresponding comments that are still
> > referencing it.
> >
> > Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> >
> > ...
> >
> > /*
> > - * Backend-specific cleanup. Defined by vhost-cuse and vhost-user.
> > + * Backend-specific cleanup.
> > + *
> > + * TODO: fix it; we have one backend now
> > */
> > void vhost_backend_cleanup(struct virtio_net *dev);
>
> In general it is not a good idea to leave TODOs/Fixmes around unless they
> that a better explanation of why they are there.
Agreed.
In this case, if you look at the delete line, you will find we have such
function implemented both in vhost-user and vhost-cuse. Now we get one
only. So, we may could just rename it to vhost_user_cleanup(). Or even,
remove it completely by doing some small refactors.
It's obvious that we need do that in another patch. Thus, the TODO is
been added.
--yliu
>
> Apart from that:
>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
>
next prev parent reply other threads:[~2016-11-04 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 3:14 [PATCH 0/3] vhost: comments and doc update due to vhost-cuse removal Yuanhan Liu
2016-11-02 3:14 ` [PATCH 1/3] doc: update vhost programming guide Yuanhan Liu
2016-11-04 13:22 ` Mcnamara, John
2016-11-02 3:15 ` [PATCH 2/3] doc: update the vhost sample guide Yuanhan Liu
2016-11-04 13:38 ` Mcnamara, John
2016-11-02 3:15 ` [PATCH 3/3] vhost: update comments Yuanhan Liu
2016-11-04 13:28 ` Mcnamara, John
2016-11-04 14:15 ` Yuanhan Liu [this message]
2016-11-07 15:00 ` [PATCH 0/3] vhost: comments and doc update due to vhost-cuse removal 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=20161104141518.GA12283@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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.