DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Patil, Harish" <Harish.Patil@cavium.com>
To: Yuanhan Liu <yliu@fridaylinux.org>
Cc: dpdk stable <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] 17.08.1 patches review and test
Date: Sat, 2 Dec 2017 17:49:05 +0000	[thread overview]
Message-ID: <D6482765.1853E3%Harish.Patil@cavium.com> (raw)
In-Reply-To: <20171201062850.GA17395@yliu-dev>



-----Original Message-----
From: Yuanhan Liu <yliu@fridaylinux.org>
Date: Thursday, November 30, 2017 at 10:28 PM
To: Harish Patil <Harish.Patil@cavium.com>
Cc: dpdk stable <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>, "Xu,
Qian Q" <qian.q.xu@intel.com>, Dept-Eng DPDK Dev
<Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] 17.08.1 patches review and test

>On Thu, Nov 30, 2017 at 07:09:28PM +0000, Patil, Harish wrote:
>> Hi Yuanhan,
>> Thanks for the queuing the patches for stable release.
>> Could you please provide ETA?
>
>Is below what you are looking for?
>
>	--yliu
>
>---
>    Hi all,
>    
>    Here is a list of patches targeted for stable release 17.08.1. Please
>==> help review and test. The planned date for the final release is 7th,
>==> Dec. Before that, please shout if anyone has objections with these
>    patches being applied.

OK thanks, we will review ASAP and get back to you.

>


  reply	other threads:[~2017-12-02 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 12:21 Yuanhan Liu
2017-11-30 19:09 ` Patil, Harish
2017-12-01  6:28   ` Yuanhan Liu
2017-12-02 17:49     ` Patil, Harish [this message]
2017-12-04 20:40 ` Patil, Harish
2017-12-07 13:46   ` Yuanhan Liu

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=D6482765.1853E3%Harish.Patil@cavium.com \
    --to=harish.patil@cavium.com \
    --cc=Dept-EngDPDKDev@cavium.com \
    --cc=dev@dpdk.org \
    --cc=qian.q.xu@intel.com \
    --cc=stable@dpdk.org \
    --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).