All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Bruce Richardson
	<bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Patch merges for 1.8 release
Date: Tue, 16 Sep 2014 16:20:21 +0200	[thread overview]
Message-ID: <2048283.MNpMd1jf3I@xps13> (raw)
In-Reply-To: <20140916101838.GA1484@BRICHA3-MOBL>

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.

-- 
Thomas

  reply	other threads:[~2014-09-16 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 10:18 Patch merges for 1.8 release Bruce Richardson
2014-09-16 14:20 ` Thomas Monjalon [this message]
2014-09-16 14:26   ` Richardson, Bruce

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=2048283.MNpMd1jf3I@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 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.