From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
David Marchand <david.marchand@6wind.com>,
Didier Pallard <didier.pallard@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Jens Freimann <jfreimann@redhat.com>,
Jianfeng Tan <jianfeng.tan@intel.com>,
Junjie Chen <junjie.j.chen@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Pawel Wodkowski <pawelx.wodkowski@intel.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Tomasz Kulasek <tomaszx.kulasek@intel.com>,
Tonghao Zhang <xiangxia.m.yue@gmail.com>,
Yongseok Koh <yskoh@mellanox.com>,
Yong Wang <yongwang@vmware.com>,
Zhiyong Yang <zhiyong.yang@intel.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.7
Date: Tue, 1 May 2018 11:49:27 +0100 [thread overview]
Message-ID: <20180501104927.10291-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 see if they are applicable to the 16.11 LTS tree, and if so
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
---
1b533790f Ajit Khaparde net/bnxt: avoid invalid vnic id in set L2 Rx mask
f4253e97e Ajit Khaparde net/bnxt: set padding flags in Rx descriptor
634d549c9 Anatoly Burakov bus/fslmc: do not needlessly check for IOVA mode
bef5a2d62 Anatoly Burakov vfio: do not needlessly check for IOVA mode
d08e3c90d Didier Pallard net/vmxnet3: fix Rx offload information in multiseg packets
30a701a53 Junjie Chen net/vhost: fix crash when creating vdev dynamically
e6722dee5 Junjie Chen net/vhost: fix invalid state
7ba5320ba Nélio Laranjeiro net/mlx5: fix link status behavior
cfee94752 Nélio Laranjeiro net/mlx5: fix link status to use wait to complete
af4f09f28 Nélio Laranjeiro net/mlx5: prefix all functions with mlx5
17c36a674 Pablo de Lara crypto/zuc: batch ops with same transform
83ade1ebd Rasesh Mody net/qede: fix device stop to remove primary MAC
ecc3fa6d3 Santosh Shukla net/octeontx: remove redundant driver name update
a1572312f Shahaf Shuler net/mlx5: enforce RSS key length limitation
a85a606ca Shahaf Shuler net/mlx5: fix link status initialization
90bb22a19 Tomasz Kulasek vhost: fix ring index returned to master on stop
b9c0dea24 Tonghao Zhang net/bonding: free mempool used in mode 6
next reply other threads:[~2018-05-01 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 10:49 luca.boccassi [this message]
2018-05-07 2:08 ` Chen, Junjie J
2018-05-08 9:50 ` Luca Boccassi
2018-05-18 9:47 ` luca.boccassi
2018-05-18 12:15 ` [dpdk-stable] [PATCH 0/4] 16.11 Requested backports Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 1/4] eal: support strlcpy function Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 2/4] bus/pci: fix size of driver name buffer Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 3/4] net/qede: fix strncpy Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 4/4] net/qede: replace strncpy by strlcpy Andy Green
2018-05-18 12:48 ` [dpdk-stable] [PATCH 0/4] 16.11 Requested backports Luca Boccassi
2018-05-25 17:24 ` [dpdk-stable] please help backporting some patches to LTS release 16.11.7 luca.boccassi
2018-05-29 21:59 ` Shaikh, Shahed
2018-05-29 22:55 ` 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=20180501104927.10291-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@6wind.com \
--cc=didier.pallard@6wind.com \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jfreimann@redhat.com \
--cc=jianfeng.tan@intel.com \
--cc=junjie.j.chen@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pawelx.wodkowski@intel.com \
--cc=rasesh.mody@cavium.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=tomaszx.kulasek@intel.com \
--cc=xiangxia.m.yue@gmail.com \
--cc=yongwang@vmware.com \
--cc=yskoh@mellanox.com \
--cc=zhiyong.yang@intel.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).