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>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Harish Patil <harish.patil@qlogic.com>,
Helin Zhang <helin.zhang@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Jianbo Liu <jianbo.liu@linaro.org>,
John Griffin <john.griffin@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Vincent Jardin <vincent.jardin@6wind.com>
Subject: [dpdk-stable] please help backporting some patches to stable release 16.11.1
Date: Mon, 23 Jan 2017 18:52:13 +0800 [thread overview]
Message-ID: <1485168733-26264-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.11,
but I failed: they can't be applied. I'm wondering can the authors check
the following list and backport some patches belong to them?
FYI, branch 16.11 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 or two
weeks. If so, please do me a favor by adding a heading line like following
before the commit log body:
[ backported from upstream commit xxx ]
Example: http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
Please let me know if you have any comments, say, need more time, or it's
worthless to packport it. And please send it to "stable@dpdk.org", but not
"dev@dpdk.org".
Thanks.
-yliu
---
7ab35bf Harish Patil net/qede: fix RSS
b7f714f Harish Patil net/qede: fix reporting PF driver as disabled
528fcfa Harish Patil net/qede: restrict maximum queues for PF/VF
786b5c2 Shahaf Shuler net/mlx5: fix multi segment packet send
54ecae2 Harish Patil net/qede: fix scatter-gather
f6033f2 Harish Patil net/qede: fix minimum buffer size and scatter Rx check
21e5e13 Bernard Iremonger net/ixgbe: fix API parameter checking
daa4c9c Ferruh Yigit net/i40e: fix VF MAC address assignment
84733fd Jerin Jacob eal/arm64: fix memory barrier definition
96ec5f9 Fiona Trahe crypto/qat: fix buffer overwrite in OOP case
next reply other threads:[~2017-01-23 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 10:52 Yuanhan Liu [this message]
2017-02-15 6:38 Yuanhan Liu
2017-02-17 13:15 ` Nélio Laranjeiro
2017-02-20 8:06 ` 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=1485168733-26264-1-git-send-email-yuanhan.liu@linux.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=harish.patil@qlogic.com \
--cc=helin.zhang@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.org \
--cc=john.griffin@intel.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=vincent.jardin@6wind.com \
/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).