patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dpdk stable <stable@dpdk.org>
Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Elad Persiko <eladpe@mellanox.com>,
	Fiona Trahe <fiona.trahe@intel.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	Qiming Yang <qiming.yang@intel.com>
Subject: [dpdk-stable] request backporting some patches to 16.07.2
Date: Tue, 15 Nov 2016 21:29:23 +0800	[thread overview]
Message-ID: <1479216563-19187-1-git-send-email-yuanhan.liu@linux.intel.com> (raw)

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-15 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 13:29 Yuanhan Liu [this message]
2016-11-21  9:38 ` Kusztal, ArkadiuszX
2016-11-21 11:31   ` Yuanhan Liu
  -- 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=1479216563-19187-1-git-send-email-yuanhan.liu@linux.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=eladpe@mellanox.com \
    --cc=fiona.trahe@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=qiming.yang@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).