patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Cc: dpdk stable <stable@dpdk.org>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"Jain, Deepak K" <deepak.k.jain@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-stable] request backporting some patches to 16.07.2
Date: Mon, 21 Nov 2016 19:31:28 +0800	[thread overview]
Message-ID: <20161121113128.GR5048@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <80307F746F1522479831AB1253B7024E709436@IRSMSX102.ger.corp.intel.com>

On Mon, Nov 21, 2016 at 09:38:45AM +0000, Kusztal, ArkadiuszX wrote:
> Hi Yuanhan,
> 
> Sorry for delayed answer.
> 
> We decided that "app/test: fix hanging in SNOW 3G performance test" fix not need to be backported.

I see. Thanks for the notice.

	--yliu

 
> Regards,
> Arek
> 
> > -----Original Message-----
> > From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> > Sent: Tuesday, November 15, 2016 1:29 PM
> > To: dpdk stable <stable@dpdk.org>
> > Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>; Adrien Mazarguil
> > <adrien.mazarguil@6wind.com>; Kusztal, ArkadiuszX
> > <arkadiuszx.kusztal@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Elad
> > Persiko <eladpe@mellanox.com>; Trahe, Fiona <fiona.trahe@intel.com>;
> > Wu, Jingjing <jingjing.wu@intel.com>; Yang, Qiming
> > <qiming.yang@intel.com>
> > Subject: request backporting some patches to 16.07.2
> > 
> > Hi commit authors (and maintainers),
> > 
> > I tried to pick following commits from upstream to stable branch 16.07, but I
> > failed: they can't be applied. I'm wondering can the authors check the list and
> > backport some patches belong to them?
> > 
> > FYI, branch 16.07 at git://dpdk.org/dpdk-stable is the place those patches
> > should be packported to. It'd be great if you could do that in one week.
> > If so, please do me a favor by adding a heading line like following before the
> > commit log body:
> > 
> >     [ backported from upstream commit xxx ]
> > 
> > Please let me know if you have any comments, say, need more time, or it's
> > worthless to packport it.
> > 
> > Thanks.
> > 
> > 	-yliu
> > 
> > ---
> > 7e70f8a  Arek Kusztal   app/test: fix hanging in SNOW 3G performance test
> > 0284624  Beilei Xing    net/i40e: fix floating VEB
> > f4668a3  Qiming Yang    net/i40e: fix link status change interrupt
> > bb6722f  Qiming Yang    net/i40e: fix VF bonded device link down
> > 609a076  Elad Persiko   net/mlx5: fix buffer alignment in Tx

  reply	other threads:[~2016-11-21 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 13:29 Yuanhan Liu
2016-11-21  9:38 ` Kusztal, ArkadiuszX
2016-11-21 11:31   ` Yuanhan Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-06  7:22 Yuanhan Liu
2016-11-15 13:58 ` Yuanhan Liu
2016-11-16 10:48   ` Maciej Czekaj
2016-11-16 11:57     ` Yuanhan Liu
2016-11-16 16:51 ` Harish Patil
2016-11-16 22:01   ` John Daley (johndale)

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=20161121113128.GR5048@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stable@dpdk.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).