From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>,
Fiona Trahe <fiona.trahe@intel.com>,
Moti Haimovsky <motih@mellanox.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Takeshi Yoshimura <t.yoshimura8869@gmail.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.8
Date: Mon, 30 Jul 2018 10:13:28 +0100 [thread overview]
Message-ID: <20180730091328.6653-1-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20180726153217.11493-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
---
64cb90f88 Fiona Trahe crypto/qat: fix checks for 3GPP algo bit params
79d098921 Moti Haimovsky net/mlx5: fix build with old kernels
a8fd8881d Pablo de Lara examples/l2fwd-crypto: skip device not supporting operation
9726c51df Rahul Lakkireddy net/cxgbe: fix init failure due to new flash parts
d4774a568 Takeshi Yoshimura vfio: fix workaround of BAR mapping
next prev parent reply other threads:[~2018-07-30 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 15:32 luca.boccassi
[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 [this message]
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=20180730091328.6653-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=dmitry.ereminsolenikov@linaro.org \
--cc=fiona.trahe@intel.com \
--cc=motih@mellanox.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=t.yoshimura8869@gmail.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).