From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: dpdk stable <stable@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Moti Haimovsky <motih@mellanox.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Randy Schacher <stuart.schacher@broadcom.com>,
Ray Jui <ray.jui@broadcom.com>,
Scott Branden <scott.branden@broadcom.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Thomas Monjalon <thomas@monjalon.net>,
Zijie Pan <zijie.pan@6wind.com>
Subject: [dpdk-stable] please help backporting some patches to stable release 18.05.1
Date: Mon, 30 Jul 2018 18:19:45 +0200 [thread overview]
Message-ID: <20180730161945.17187-1-christian.ehrhardt@canonical.com> (raw)
Hi commit authors (and maintainers),
I didn't manage to apply following commits from upstream to stable branch
18.05: conflict happens. I'm wondering can the authors check the following
list and backport those patches belong to you?
FYI, branch 18.05 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 stable in the subject line, as we have more than one
at the same time, for example:
[PATCH 18.05] foo/bar: fix baz
With git send-email, this can be achieved by appending the parameter:
--subject-prefix='18.05'
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.
Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
14255b351 Ajit Khaparde net/bnxt: fix queue start/stop operations
64cb90f88 Fiona Trahe crypto/qat: fix checks for 3GPP algo bit params
79d098921 Moti Haimovsky net/mlx5: fix build with old kernels
5366074b0 Nelio Laranjeiro net/mlx5: fix route Netlink message overflow
4487cfa1f Pablo de Lara crypto/virtio: fix memory leak
reply other threads:[~2018-07-30 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180730161945.17187-1-christian.ehrhardt@canonical.com \
--to=christian.ehrhardt@canonical.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dmitry.ereminsolenikov@linaro.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=motih@mellanox.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=ray.jui@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=shahafs@mellanox.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=stuart.schacher@broadcom.com \
--cc=thomas@monjalon.net \
--cc=zijie.pan@6wind.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).