[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

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

---
5394547798  Konstantin Ananyev acl: forbid rule with priority zero
f9de87187b  Shahaf Shuler    net/mlx5: disable ConnectX-4 Lx Multi Packet Send by default
e1110e9776  Chas Williams    net/bonding: fix Rx slave fairness
3c4c76cf17  Damjan Marion    net/i40e: fix 25G AOC and ACC cable detection on XXV710
cb71992793  Rasesh Mody      net/qede/base: fix to handle stag update event
318d7da312  Shahed Shaikh    net/qede: fix Rx buffer size calculation

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

On Wed, 2018-10-03 at 17:55 +0100, Luca Boccassi wrote:
> 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=c48313
> 94c7d1944d8ec27d52c22997f20d19718e
> 
> 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
> 
> ---
> 5394547798  Konstantin Ananyev acl: forbid rule with priority zero
> f9de87187b  Shahaf Shuler    net/mlx5: disable ConnectX-4 Lx Multi
> Packet Send by default
> e1110e9776  Chas Williams    net/bonding: fix Rx slave fairness
> 3c4c76cf17  Damjan Marion    net/i40e: fix 25G AOC and ACC cable
> detection on XXV710

This i40e patch requires this other which was not marked for
backporting:

fa94e11bb9 net/i40e/base: add capability macros

Qi, are you OK with having these 2 backported to 16.11?

-- 
Kind regards,
Luca Boccassi

[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

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

---
b1621823ea  Anatoly Burakov  mem: fix undefined behavior in NUMA-aware mapping
738ad7b42b  Fiona Trahe      test/crypto: fix number of queue pairs
1037ed842c  Jerin Jacob      mbuf: fix Tx offload mask
729199397f  Jiayu Hu         vhost: fix corner case for enqueue operation
cb0ad8fa26  Paul M Stillwell Jr ethdev: fix doxygen comment to be with structure
54f4a22dc1  Qi Zhang         net/i40e/base: improve the polling mechanism
b72611a274  Qi Zhang         net/i40e/base: read LLDP config area with correct endianness
7486331308  Radu Nicolau     net/bonding: stop and deactivate slaves on stop
d469f6a5eb  Shahaf Shuler    net/mlx5: add representor specific statistics
1a611fdaf6  Shahaf Shuler    net/mlx5: support missing counter in extended statistics
51fafb89a9  Somnath Kotur    net/bnxt: get rid of ff pools and use VNIC info array
8f3ea0a03d  Thomas Monjalon  devtools: fix printing subject of checked patch
ff37ca5d37  Thomas Monjalon  devtools: use a common prefix for temporary files
66908eff12  Tiwei Bie        net/virtio: add missing supported features

[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

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

---
630deed61  Alejandro Lucero bus/pci: compare kernel driver instead of interrupt handler
c23e46594  Jerin Jacob      mbuf: fix offload flag name and list
f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for undefined operation
effdb8bbb  Phil Yang        app/testpmd: fix physical port socket initialization
298413364  Phil Yang        app/testpmd: fix vdev socket initialization
a569af248  Phil Yang        app/testpmd: reserve NUMA node per port and per ring

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[yoursunny]

Hi Luca

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
>
> f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for undefined
> operation


My commit is irrelevant to DPDK 16.11. I’m fixing a small bug introduced
after DPDK gains asymmetric crypto feature. Back then DPDK does not support
assymetric crypto.

> Yours, Junxiao

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

On Thu, 2018-11-01 at 07:21 -0400, yoursunny wrote:
> Hi Luca
> 
> 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
> > 
> > f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for
> > undefined
> > operation
> 
> 
> My commit is irrelevant to DPDK 16.11. I’m fixing a small bug
> introduced
> after DPDK gains asymmetric crypto feature. Back then DPDK does not
> support
> assymetric crypto.
> 
> > Yours, Junxiao

Hi,

Ok, false positive in the selection script, thanks for checking.

-- 
Kind regards,
Luca Boccassi

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Phil Yang (Arm Technology China)]

Hi Luca,

I have done my part. Please check it. Thanks!

Thanks,
Phil Yang

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Thursday, November 1, 2018 7:11 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Akhil Goyal <akhil.goyal@nxp.com>; Alejandro Lucero
> <alejandro.lucero@netronome.com>; Anatoly Burakov
> <anatoly.burakov@intel.com>; Andrew Rybchenko
> <arybchenko@solarflare.com>; Gavin Hu (Arm Technology China)
> <Gavin.Hu@arm.com>; Jerin Jacob <jerin.jacob@caviumnetworks.com>;
> Junxiao Shi <git@mail1.yoursunny.com>; Konstantin Ananyev
> <konstantin.ananyev@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>; Natalie Samsonov
> <nsamsono@marvell.com>; Phil Yang (Arm Technology China)
> <Phil.Yang@arm.com>; Shreyansh Jain <shreyansh.jain@nxp.com>; Tianfei
> Zhang <tianfei.zhang@intel.com>; Tiwei Bie <tiwei.bie@intel.com>; Yelena
> Krivosheev <yelena@marvell.com>
> Subject: please help backporting some patches to LTS release 16.11.9
>
> 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
>
> ---
> 630deed61  Alejandro Lucero bus/pci: compare kernel driver instead of interrupt
> handler
> c23e46594  Jerin Jacob      mbuf: fix offload flag name and list
> f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for undefined
> operation
> effdb8bbb  Phil Yang        app/testpmd: fix physical port socket initialization
> 298413364  Phil Yang        app/testpmd: fix vdev socket initialization
> a569af248  Phil Yang        app/testpmd: reserve NUMA node per port and per
> ring
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

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

---
b1621823e  Anatoly Burakov  mem: fix undefined behavior in NUMA-aware mapping
054d1be48  Beilei Xing      net/i40e: fix Rx instability with vector mode
c23e46594  Jerin Jacob      mbuf: fix offload flag name and list
1037ed842  Jerin Jacob      mbuf: fix Tx offload mask
f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for undefined operation
54f4a22dc  Qi Zhang         net/i40e/base: improve the polling mechanism
b72611a27  Qi Zhang         net/i40e/base: read LLDP config area with correct endianness
cb7199279  Rasesh Mody      net/qede/base: fix to handle stag update event
d469f6a5e  Shahaf Shuler    net/mlx5: add representor specific statistics
f9de87187  Shahaf Shuler    net/mlx5: disable ConnectX-4 Lx Multi Packet Send by default
1a611fdaf  Shahaf Shuler    net/mlx5: support missing counter in extended statistics
318d7da31  Shahed Shaikh    net/qede: fix Rx buffer size calculation
51fafb89a  Somnath Kotur    net/bnxt: get rid of ff pools and use VNIC info array

[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

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

---
0c15f3c01  Ali Alnubani     net/mlx5: fix initialization of struct members
5835b7d37  Pallantla Poornima test/kni: fix module miss fallback
853c78249  Rasesh Mody      net/bnx2x: fix dynamic logging

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Ali Alnubani]

Hi Luca,

The following patches are not applicable in the stable branches (Please ignore them):

net/mlx5: fix initialization of struct members http://patches.dpdk.org/patch/48051/ 
net/mlx4: fix initialization of struct members http://patches.dpdk.org/patch/48050/ 
net/mlx5: fix typos http://patches.dpdk.org/patch/48057/ 
net/mlx4: fix typo http://patches.dpdk.org/patch/48056/ 

I apologize for the mistake. 

Thanks,
Ali

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Monday, November 26, 2018 2:21 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Ali Alnubani <alialnu@mellanox.com>; Ferruh Yigit
> <ferruh.yigit@intel.com>; Gavin Hu <gavin.hu@arm.com>; Pallantla
> Poornima <pallantlax.poornima@intel.com>; Rasesh Mody
> <rasesh.mody@cavium.com>; Reshma Pattan <reshma.pattan@intel.com>;
> Shahaf Shuler <shahafs@mellanox.com>; Stephen Hemminger
> <stephen@networkplumber.org>
> Subject: please help backporting some patches to LTS release 16.11.9
> 
> 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:
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> k.org%2Fbrowse%2Fdpdk-
> stable%2Fcommit%2F%3Fh%3D16.07%26id%3Dc4831394c7d1944d8ec27d52c2
> 2997f20d19718e&amp;data=02%7C01%7Calialnu%40mellanox.com%7Cbcb51
> 6933b654626b23308d65399ae64%7Ca652971c7d2e4d9ba6a4d149256f461b%7
> C0%7C0%7C636788316868045140&amp;sdata=y3qFnX%2BVeoCE%2FbjkQNjF
> s4DuBo89w0jhC4%2F%2FS126LHQ%3D&amp;reserved=0
> 
> 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
> 
> ---
> 0c15f3c01  Ali Alnubani     net/mlx5: fix initialization of struct members
> 5835b7d37  Pallantla Poornima test/kni: fix module miss fallback
> 853c78249  Rasesh Mody      net/bnx2x: fix dynamic logging

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

On Tue, 2018-11-27 at 12:55 +0000, Ali Alnubani wrote:
> Hi Luca,
> 
> The following patches are not applicable in the stable branches
> (Please ignore them):
> 
> net/mlx5: fix initialization of struct members http://patches.dpdk.or
> g/patch/48051/ 
> net/mlx4: fix initialization of struct members http://patches.dpdk.or
> g/patch/48050/ 
> net/mlx5: fix typos http://patches.dpdk.org/patch/48057/ 
> net/mlx4: fix typo http://patches.dpdk.org/patch/48056/ 
> 
> I apologize for the mistake. 
> 
> Thanks,
> Ali

No worries, thanks for checking.

> > -----Original Message-----
> > From: Luca Boccassi <bluca@debian.org>
> > Sent: Monday, November 26, 2018 2:21 PM
> > To: dpdk stable <stable@dpdk.org>
> > Cc: Ali Alnubani <alialnu@mellanox.com>; Ferruh Yigit
> > <ferruh.yigit@intel.com>; Gavin Hu <gavin.hu@arm.com>; Pallantla
> > Poornima <pallantlax.poornima@intel.com>; Rasesh Mody
> > <rasesh.mody@cavium.com>; Reshma Pattan <reshma.pattan@intel.com>;
> > Shahaf Shuler <shahafs@mellanox.com>; Stephen Hemminger
> > <stephen@networkplumber.org>
> > Subject: please help backporting some patches to LTS release
> > 16.11.9
> > 
> > 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:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fd
> > pd
> > k.org%2Fbrowse%2Fdpdk-
> > stable%2Fcommit%2F%3Fh%3D16.07%26id%3Dc4831394c7d1944d8ec27d52c2
> > 2997f20d19718e&amp;data=02%7C01%7Calialnu%40mellanox.com%7Cbcb51
> > 6933b654626b23308d65399ae64%7Ca652971c7d2e4d9ba6a4d149256f461b%7
> > C0%7C0%7C636788316868045140&amp;sdata=y3qFnX%2BVeoCE%2FbjkQNjF
> > s4DuBo89w0jhC4%2F%2FS126LHQ%3D&amp;reserved=0
> > 
> > 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
> > 
> > ---
> > 0c15f3c01  Ali Alnubani     net/mlx5: fix initialization of struct
> > members
> > 5835b7d37  Pallantla Poornima test/kni: fix module miss fallback
> > 853c78249  Rasesh Mody      net/bnx2x: fix dynamic logging

-- 
Kind regards,
Luca Boccassi

[dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Luca Boccassi]

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

Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9

[Ilya Maximets]

Hi Luca,
Regarding commit 705dced4a ("net/virtio: avoid annoying IOPL error log").
This annoying message itself exists since very old times, but it's not
really printed until v18.02 where the logging system was changed.
So, I think, you may skip the patch for backporting to 16.11.

Best regards, Ilya Maximets.

On 28.11.2018 13:02, Luca Boccassi wrote:
> 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
> 
>