From: Luca Boccassi <bluca@debian.org>
To: dpdk stable <stable@dpdk.org>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Darek Stojaczyk <dariusz.stojaczyk@intel.com>,
David Marchand <david.marchand@redhat.com>,
Ilya Maximets <i.maximets@samsung.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Shahed Shaikh <shahed.shaikh@cavium.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 16.11.9
Date: Wed, 28 Nov 2018 10:02:02 +0000 [thread overview]
Message-ID: <20181128100202.27663-1-bluca@debian.org> (raw)
In-Reply-To: <20181126122113.8568-1-bluca@debian.org>
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
---
047e3f9f2 Darek Stojaczyk vfio: do not needlessly setup device in secondary process
705dced4a Ilya Maximets net/virtio: avoid annoying IOPL error log
3985ea528 Shahed Shaikh net/qede: fix Tx offload mask
next prev parent reply other threads:[~2018-11-28 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 16:55 Luca Boccassi
2018-10-03 16:57 ` Luca Boccassi
2018-10-18 8:37 ` Luca Boccassi
2018-11-01 11:11 ` Luca Boccassi
2018-11-01 11:21 ` yoursunny
2018-11-01 11:25 ` Luca Boccassi
2018-11-02 7:51 ` Phil Yang (Arm Technology China)
2018-11-19 10:56 ` Luca Boccassi
2018-11-26 12:21 ` Luca Boccassi
2018-11-27 12:55 ` Ali Alnubani
2018-11-27 18:49 ` Luca Boccassi
2018-11-28 10:02 ` Luca Boccassi [this message]
2018-11-28 10:11 ` Ilya Maximets
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=20181128100202.27663-1-bluca@debian.org \
--to=bluca@debian.org \
--cc=anatoly.burakov@intel.com \
--cc=dariusz.stojaczyk@intel.com \
--cc=david.marchand@redhat.com \
--cc=i.maximets@samsung.com \
--cc=maxime.coquelin@redhat.com \
--cc=shahed.shaikh@cavium.com \
--cc=stable@dpdk.org \
/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).