From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Aaron Conole <aconole@redhat.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Alex Smith <alex.smith@example.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Chas Williams <chas3@att.com>, Hyong Youb Kim <hyonkim@cisco.com>,
Ilya Maximets <i.maximets@samsung.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
John Daley <johndale@cisco.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Narender Vangati <narender.vangati@intel.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Nikhil Rao <nikhil.rao@intel.com>, Peng He <xnhp0320@icloud.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Shahed Shaikh <shahed.shaikh@cavium.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.8
Date: Thu, 26 Jul 2018 16:32:17 +0100 [thread overview]
Message-ID: <20180726153217.11493-1-luca.boccassi@gmail.com> (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 in one or two weeks. Also, please add a
heading line like below before the commit log body:
[ backported from upstream commit xxx ]
Example: http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
Also please mention the target LTS in the subject line, as we have more than one
at the same time, for example:
[PATCH 16.11] foo/bar: fix baz
With git send-email, this can be achieved by appending the parameter:
--subject-prefix='16.11'
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.
Luca Boccassi
---
3c2e87c10 Ajit Khaparde net/bnxt: fix close operation
0b82bd7b2 Anatoly Burakov memzone: improve zero-length reserve
0e677a353 Chas Williams net/bonding: always update bonding link status
2a7e3d546 Hyong Youb Kim net/enic: do not overwrite admin Tx queue limit
e11411b52 Maxime Coquelin vhost: fix missing increment of log cache count
c44fbc7cc Nelio Laranjeiro net/mlx5: clean-up developer logs
6b83f5935 Nikhil Rao eventdev: add event buffer flush in Rx adapter
a16aef523 Rasesh Mody net/qede: fix for devargs
7105b24f4 Rasesh Mody net/qede: fix memory alloc for multiple port reconfig
d121a6b5f Rasesh Mody net/qede: fix VF MTU update
475ff2895 Rasesh Mody net/qede: remove primary MAC removal
e46821e9f Shahaf Shuler net/mlx5: separate generic tunnel TSO from the standard one
245aec289 Shahed Shaikh net/qede: fix legacy interrupt mode
cfab13aa9 Shahed Shaikh net/qede: fix link change event notification
c7641841a Shahed Shaikh net/qede: fix unicast MAC address handling in VF
next reply other threads:[~2018-07-26 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 15:32 luca.boccassi [this message]
[not found] ` <C6ECDF3AB251BE4894318F4E451236978247D952@IRSMSX109.ger.corp.intel.com>
2018-07-26 16:06 ` Luca Boccassi
2018-07-29 6:03 ` Shahaf Shuler
2018-07-30 8:54 ` Luca Boccassi
2018-07-30 9:13 ` luca.boccassi
2018-07-30 10:29 ` Burakov, Anatoly
2018-07-30 10:39 ` Luca Boccassi
2018-07-30 13:58 ` Rahul Lakkireddy
2018-07-30 16:02 ` Luca Boccassi
2018-08-08 15:19 ` luca.boccassi
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=20180726153217.11493-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=alex.smith@example.com \
--cc=anatoly.burakov@intel.com \
--cc=chas3@att.com \
--cc=hyonkim@cisco.com \
--cc=i.maximets@samsung.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=johndale@cisco.com \
--cc=maxime.coquelin@redhat.com \
--cc=narender.vangati@intel.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=nikhil.rao@intel.com \
--cc=rasesh.mody@cavium.com \
--cc=shahafs@mellanox.com \
--cc=shahed.shaikh@cavium.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=xnhp0320@icloud.com \
--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).