From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Yuanhan Liu <yliu@fridaylinux.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [git pull] virtio changes for 17.11-rc1
Date: Fri, 6 Oct 2017 11:50:30 +0100 [thread overview]
Message-ID: <20171006105030.GA25712@bricha3-MOBL3.ger.corp.intel.com> (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?
>
Just my 2c here, is that there is currently a lot of code merged to the
*-next trees that is staged for the mainline, so whatever state it is
in, I'd like to see it all pulled ASAP. That way we all can work off a
common baseline.
Perhaps for the 18.02 release, we can see more frequent
pulls of the subtrees, so as to avoid having unsynced patches throughout
all trees?
/Bruce
next prev parent reply other threads:[~2017-10-06 10:50 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 [this message]
2017-10-06 12:04 ` Thomas Monjalon
2017-10-06 11:05 ` Yuanhan Liu
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=20171006105030.GA25712@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--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).