From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
Andy Green <andy@warmcat.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Declan Doherty <declan.doherty@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Kirill Rybalchenko <kirill.rybalchenko@intel.com>,
Matan Azrad <matan@mellanox.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Reshma Pattan <reshma.pattan@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.7
Date: Fri, 18 May 2018 10:47:26 +0100 [thread overview]
Message-ID: <20180518094726.30066-1-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20180501104927.10291-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='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
---
52f711f7b Andy Green bus/pci: fix size of driver name buffer
fe5f777b5 Andy Green bus/pci: replace strncpy by strlcpy
f28742ba0 Andy Green net/qede: fix strncpy
0fa4f3eee Andy Green net/qede: replace strncpy by strlcpy
1bdea6110 Kirill Rybalchenko examples/ipsec-secgw: fix IP address parsing
bafa9aa0d Matan Azrad ethdev: fix port removal notification timing
59056833c Matan Azrad net/bonding: fix slave activation simultaneously
ae943ebe1 Reshma Pattan examples/ipsec-secgw: replace strncpy with strlcpy
next prev parent reply other threads:[~2018-05-18 9:47 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 [this message]
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=20180518094726.30066-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=andy@warmcat.com \
--cc=arybchenko@solarflare.com \
--cc=cristian.dumitrescu@intel.com \
--cc=declan.doherty@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=kirill.rybalchenko@intel.com \
--cc=matan@mellanox.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).