From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Jay Ding <jay.ding@broadcom.com>,
Randy Schacher <stuart.schacher@broadcom.com>,
Ray Jui <ray.jui@broadcom.com>,
Scott Branden <scott.branden@broadcom.com>
Subject: [dpdk-stable] please help backporting some patches to stable release 18.02.2
Date: Fri, 25 May 2018 18:23:44 +0100 [thread overview]
Message-ID: <20180525172344.21788-1-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20180518094648.29733-1-luca.boccassi@gmail.com>
Hi commit authors (and maintainers),
I didn't manage to apply following commits from upstream to stable branch
18.02: conflict happens. I'm wondering can the authors check the following
list and backport those patches belong to you?
FYI, branch 18.02 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.02] foo/bar: fix baz
With git send-email, this can be achieved by appending the parameter:
--subject-prefix='PATCH 18.02'
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
---
5ff6aa243 Adrien Mazarguil app/testpmd: fix copy of raw flow item - revisited
a68e95fac Adrien Mazarguil ethdev: fix shallow copy of flow API RAW item
27bdbbef1 Adrien Mazarguil net/mlx4: fix default in RSS converter
44cbeffe7 Ajit Khaparde net/bnxt: fix RSS hash configuration
edafb57ba Ajit Khaparde net/bnxt: fix VF resource allocation
prev parent reply other threads:[~2018-05-25 17:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:23 luca.boccassi
2018-04-30 15:30 ` Maxime Coquelin
2018-04-30 15:44 ` Luca Boccassi
2018-04-30 16:06 ` Burakov, Anatoly
2018-04-30 16:33 ` Luca Boccassi
2018-05-02 6:04 ` Hyong Youb Kim
2018-05-02 10:43 ` Luca Boccassi
2018-05-02 8:27 ` Nélio Laranjeiro
2018-05-02 10:42 ` Luca Boccassi
2018-05-18 9:46 ` luca.boccassi
2018-05-18 10:11 ` Richardson, Bruce
2018-05-18 10:21 ` Luca Boccassi
2018-05-18 10:25 ` Andy Green
2018-05-18 10:33 ` Pattan, Reshma
2018-05-18 10:36 ` Andy Green
2018-05-18 11:37 ` [dpdk-stable] [PATCH 0/5] 18.02 Requested backports Andy Green
2018-05-18 11:37 ` [dpdk-stable] [PATCH 1/5] eal: support strlcpy function Andy Green
2018-05-18 11:37 ` [dpdk-stable] [PATCH 2/5] bus/pci: fix size of driver name buffer Andy Green
2018-05-18 11:38 ` [dpdk-stable] [PATCH 3/5] net/qede: fix strncpy Andy Green
2018-05-18 11:38 ` [dpdk-stable] [PATCH 4/5] net/qede: replace strncpy by strlcpy Andy Green
2018-05-18 11:38 ` [dpdk-stable] [PATCH 5/5] net/sfc: make sure that stats name is nul-terminated Andy Green
2018-05-18 13:13 ` [dpdk-stable] [PATCH 0/5] 18.02 Requested backports Luca Boccassi
2018-05-25 17:23 ` luca.boccassi [this message]
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=20180525172344.21788-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=jay.ding@broadcom.com \
--cc=ray.jui@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=stable@dpdk.org \
--cc=stuart.schacher@broadcom.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).