DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yliu@fridaylinux.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dpdk stable <stable@dpdk.org>,
	dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] 17.11.3 (LTS) patches review and test
Date: Fri, 08 Jun 2018 23:20:01 +0800	[thread overview]
Message-ID: <1528471201.968257.1401119784.0F3305D8@webmail.messagingengine.com> (raw)
In-Reply-To: <20180608150043.GA21352@bricha3-MOBL.ger.corp.intel.com>



On Fri, Jun 8, 2018, at 11:00 PM, Bruce Richardson wrote:
> On Sun, May 27, 2018 at 01:35:17PM +0800, Yuanhan Liu wrote:
> > Hi all,
> > 
> > Here is a list of patches targeted for LTS release 17.11.3. Please
> > help review and test. The planned date for the final release is 8th,
> > Jun. Before that, please let me know if anyone has objections with
> > these patches being applied.
> > 
> > These patches are located at branch 17.11 of dpdk-stable repo:
> >     http://dpdk.org/browse/dpdk-stable/
> > 
> > Thanks.
> > 
> > 	--yliu
> > 
> Hi Yuanhan,
> 
> while I understand that you are eager to get the release out, I don't
> believe all testing has been completed by us on the patches. Can the
> release be postponed by a few days to allow the testing to be completed.


Hi Bruce,

Sure, no problem, I will postpone it to next Friday. Hope it's okay to you guys.

And thanks for the testing!

        --yliu

      reply	other threads:[~2018-06-08 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-27  5:35 Yuanhan Liu
2018-05-28 10:16 ` [dpdk-dev] [dpdk-stable] " Kevin Traynor
2018-06-07 23:09 ` [dpdk-dev] " Raslan Darawsheh
2018-06-08 14:29   ` Yuanhan Liu
2018-06-08 15:00 ` Bruce Richardson
2018-06-08 15:20   ` Yuanhan Liu [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=1528471201.968257.1401119784.0F3305D8@webmail.messagingengine.com \
    --to=yliu@fridaylinux.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@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).