From: Thomas Monjalon <thomas@monjalon.net>
To: Jianfeng Tan <jianfeng.tan@intel.com>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
yliu@fridaylinux.org, tiwei.bie@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/3] Some fixes on virtio-user/vhost
Date: Tue, 13 Feb 2018 18:55:10 +0100 [thread overview]
Message-ID: <7259085.1E0trEnmhp@xps> (raw)
In-Reply-To: <dea517df-9aee-d228-c4d0-0d3ad6bedb29@redhat.com>
13/02/2018 14:32, Maxime Coquelin:
>
> On 02/12/2018 04:20 AM, Jianfeng Tan wrote:
> > Patch 1: a trivial fix on reword a log message.
> > Patch 2: fix the rxq interrupt mode when virtio-user is used
> > with vhost kernel.
> > Patch 3: a trivial fix on LSC fd init when virtio-user is used
> > with vhost kernel.
> >
> > Jianfeng Tan (3):
> > net/vhost: fix incorrect log info
> > net/virtio-user: fix not working with vhost kernel
> > net/virtio-user: fix not proper initialized
>
> For the series:
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Thomas, I would suggest to pick this series for v18.02, as patch 2 fixes
> a bug introduced in this release cycle.
Applied with these reworded titles:
net/vhost: fix log messages on create/destroy
net/virtio-user: fix start with kernel vhost
net/virtio-user: fix interrupts with kernel vhost
prev parent reply other threads:[~2018-02-13 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 3:20 Jianfeng Tan
2018-02-12 3:20 ` [dpdk-dev] [PATCH 1/3] net/vhost: fix incorrect log info Jianfeng Tan
2018-02-12 3:20 ` [dpdk-dev] [PATCH 2/3] net/virtio-user: fix not working with vhost kernel Jianfeng Tan
2018-02-12 3:20 ` [dpdk-dev] [PATCH 3/3] net/virtio-user: fix not proper initialized Jianfeng Tan
2018-02-13 13:32 ` [dpdk-dev] [PATCH 0/3] Some fixes on virtio-user/vhost Maxime Coquelin
2018-02-13 17:55 ` Thomas Monjalon [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=7259085.1E0trEnmhp@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=yliu@fridaylinux.org \
/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).