From: Yuanhan Liu <yliu@fridaylinux.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [git pull] virtio changes for 17.11-rc1
Date: Fri, 6 Oct 2017 19:05:07 +0800 [thread overview]
Message-ID: <20171006110506.GF1545@yliu-home> (raw)
In-Reply-To: <6013017.jYmzBqReqL@xps>
On Fri, Oct 06, 2017 at 11:47:27AM +0200, Thomas Monjalon wrote:
> 06/10/2017 08:45, Yuanhan Liu:
> > Hi Thomas,
> >
> > Please consider pulling following virtio changes for 17.11-rc1 at
> > git://dpdk.org/next/dpdk-next-virtio master
>
> What about the other virtio/vhost patches pending in patchwork?
Due to my bad: not reviewing them in time, they are not in this pull
request. I will consider to merge them (if they are good) later (say
rc2). OTOH, I just saw 6 patches are pending in my list (and 2 of
them are very old, that they are not in my list for this release).
One big patchset hasn't been merged yet is the generic interface for
vdev multiple process model. I still have some comments about the
vhost part, thus it's not included in this pull request. It was also
asked for more review about the EAL changes. Also, it may not be
my duty to send merge this patchset: the core changes lie in EAL
and vdev bus.
--yliu
next prev parent reply other threads:[~2017-10-06 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 6:45 Yuanhan Liu
2017-10-06 9:47 ` Thomas Monjalon
2017-10-06 10:50 ` Bruce Richardson
2017-10-06 12:04 ` Thomas Monjalon
2017-10-06 11:05 ` Yuanhan Liu [this message]
2017-10-07 14:37 ` Thomas Monjalon
2017-10-07 14:57 ` Thomas Monjalon
2017-10-09 8:20 ` Maxime Coquelin
2017-10-08 20:10 ` Olivier MATZ
2017-10-08 20:16 ` Thomas Monjalon
2017-10-09 2:43 ` Yuanhan Liu
2017-10-09 7:13 ` Maxime Coquelin
2017-10-09 2:55 ` Yuanhan Liu
2017-10-09 7:13 ` Maxime Coquelin
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=20171006110506.GF1545@yliu-home \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).