From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Patch merges for 1.8 release
Date: Tue, 16 Sep 2014 14:26:07 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0343F27B0@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2048283.MNpMd1jf3I@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, September 16, 2014 3:20 PM
> To: Richardson, Bruce
> Cc: dev@dpdk.org
> Subject: Re: Patch merges for 1.8 release
>
> Hi Bruce,
>
> 2014-09-16 11:18, Bruce Richardson:
> > I'm just wondering what the expected timeline is for you starting to merge
> patches in for the 1.8 release? As you have
> > probably seen, I have quite a number of outstanding patches submitted for
> mbufs, and I'm wonder when the "part 1" set,
> > which by now has been pretty well reviewed and ack'ed, might be merged to
> the mainline? I'm loath to start upstreaming
> > drafts of part 3 patches at this stage, because the depth of the backlog I'm
> building up just increases the amount
> > of work I have to do for any mainline changes that require me to do changes
> on rebase.
>
> I was very busy last week with DPDK summit and IDF.
> Now I'm back and I'm cleaning up the patchwork tool (before availability
> announcement in a couple of days).
> Then the goal of the next days is to make a -rc1 tag with all the patches
> which are ready and properly reviewed.
> The mbuf changes are first in my list.
>
Thanks for the info, and welcome back!
/Bruce
prev parent reply other threads:[~2014-09-16 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 10:18 Bruce Richardson
2014-09-16 14:20 ` Thomas Monjalon
2014-09-16 14:26 ` Richardson, Bruce [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=59AF69C657FD0841A61C55336867B5B0343F27B0@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).