From: Yuanhan Liu <yliu@fridaylinux.org>
To: dpdk stable <stable@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Jeff Guo <jia.guo@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,
Matan Azrad <matan@mellanox.com>,
Mike Stolarchuk <mike.stolarchuk@bigswitch.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Yongseok Koh <yskoh@mellanox.com>,
Yuanhan Liu <yliu@fridaylinux.org>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.3
Date: Mon, 14 Aug 2017 20:18:17 +0800 [thread overview]
Message-ID: <20170814121817.GR9612@yliu-home> (raw)
Hi commit authors (and maintainers),
I didn't manage to apply following commits from upstream to stable branch
16.11: conflict happens. I'm wondering can the authors check the following
list and backport those patches belong to you?
FYI, branch 16.11 is located at tree:
git://dpdk.org/dpdk-stable
It'd be great if you could do that before the end of this week. Any thing
later than that will be missed in this release and be candidates for next
LTS release.
Please add a heading line like below before the commit log body while
backporting:
[ backported from upstream commit full_commit_hash ]
Example: http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
Please let me know if you have any comments. And please send it to
"stable@dpdk.org", but not "dev@dpdk.org".
Thanks.
-yliu
---
2d449f7 Adrien Mazarguil net/mlx4: fix assertion failure on link update
28eef5e Ajit Khaparde net/bnxt: enable default VNIC allocation
2bda4ec Ajit Khaparde net/bnxt: fix vnic cleanup
1bb8f66 Jeff Guo net/i40e: fix link down and negotiation
1859934 Jeff Guo net/i40e: fix VF add/del MAC
d58244b Jingjing Wu net/i40e: fix LSC interrupt
53d49d8 Jingjing Wu net/ixgbe: fix LSC interrupt
8d0f801 Matan Azrad net/mlx4: fix probe failure report
61d04ef Mike Stolarchuk hash: fix lock release on add
a0edafe Nelio Laranjeiro net/mlx5: fix MTU update
5668da1 Pablo de Lara crypto/qat: fix HMAC supported key sizes
b5b047a Pablo de Lara crypto/qat: fix SHA384-HMAC block size
8082845 Pablo de Lara doc: remove incorrect limitation on AESNI-MB PMD
de938b7 Pablo de Lara doc: remove incorrect limitation on QAT PMD
f2522ce Pablo de Lara test/crypto: fix wrong AAD setting
48dfc20 Yongseok Koh net/mlx5: fix missing packet type calculation
next reply other threads:[~2017-08-14 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 12:18 Yuanhan Liu [this message]
2017-08-31 9:44 ` [dpdk-stable] [PATCH 0/2] back-ported Mellanox fixes for stable Adrien Mazarguil
2017-08-31 9:44 ` [dpdk-stable] [PATCH 1/2] net/mlx: remove link update lock Adrien Mazarguil
2017-08-31 9:44 ` [dpdk-stable] [PATCH 2/2] net/mlx4: fix assertion failure on link update Adrien Mazarguil
2017-09-01 2:00 ` [dpdk-stable] [PATCH 0/2] back-ported Mellanox fixes for stable 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=20170814121817.GR9612@yliu-home \
--to=yliu@fridaylinux.org \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=matan@mellanox.com \
--cc=mike.stolarchuk@bigswitch.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).