From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Harish Patil <harish.patil@cavium.com>,
Lei Yao <lei.a.yao@intel.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Qingmin Liu <qingmin.liu@broadcom.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Shahed Shaikh <shahed.shaikh@cavium.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Zhiyong Yang <zhiyong.yang@intel.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.7
Date: Fri, 25 May 2018 18:24:33 +0100 [thread overview]
Message-ID: <20180525172433.22109-1-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20180518094726.30066-1-luca.boccassi@gmail.com>
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='PATCH 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
---
44cbeffe7 Ajit Khaparde net/bnxt: fix RSS hash configuration
2b947bd29 Ajit Khaparde net/bnxt: use first completion ring for fwd and async event
413ecf294 Harish Patil net/qede: fix multicast filtering
124909d7e Zhiyong Yang app/testpmd: fix exit for virtio-user
next prev parent reply other threads:[~2018-05-25 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 10:49 luca.boccassi
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 ` luca.boccassi [this message]
2018-05-29 21:59 ` [dpdk-stable] please help backporting some patches to LTS release 16.11.7 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=20180525172433.22109-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bernard.iremonger@intel.com \
--cc=harish.patil@cavium.com \
--cc=lei.a.yao@intel.com \
--cc=mst@redhat.com \
--cc=qingmin.liu@broadcom.com \
--cc=rasesh.mody@cavium.com \
--cc=shahed.shaikh@cavium.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.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).