patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 20.11.5
@ 2022-03-15 13:33 luca.boccassi
  0 siblings, 0 replies; 7+ messages in thread
From: luca.boccassi @ 2022-03-15 13:33 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2022/03/18.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 20.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 20.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 20.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
f65c7fbcec  Devendra Singh Rawat net/qede: fix Rx bulk
c1d1b94eec  Gerry Gribbon    app/regex: fix number of matches
a058de216c  Gregory Etelson  app/testpmd: fix GTP header parsing in checksum engine

^ permalink raw reply	[flat|nested] 7+ messages in thread
* please help backporting some patches to stable release 20.11.5
@ 2022-03-09 16:38 luca.boccassi
  0 siblings, 0 replies; 7+ messages in thread
From: luca.boccassi @ 2022-03-09 16:38 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 03/16/22.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 20.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 20.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

Thanks.

Luca Boccassi

---
dc065d6efd  Adham Masarwah   net/mlx5: fix destroying empty matchers list
655c3c26c1  Dmitry Kozlyuk   net/mlx5: fix initial link status detection
17f95513ad  Dmitry Kozlyuk   net/mlx5: fix link status change detection
4bab7ea60c  Karl Bonde Torp  build: fix build on FreeBSD with Meson 0.61.1
9267617bb0  Shun Hao         net/mlx5: fix meter policy creation assert
20659eb380  Wei Huang        raw/ifpga: fix interrupt handle allocation

^ permalink raw reply	[flat|nested] 7+ messages in thread
* please help backporting some patches to stable release 20.11.5
@ 2022-02-28 21:31 luca.boccassi
       [not found] ` <20220228213154.3344354-1-luca.boccassi@gmail.com>
  0 siblings, 1 reply; 7+ messages in thread
From: luca.boccassi @ 2022-02-28 21:31 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 03/07/22.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 20.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 20.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 20.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
033904450b  Chengwen Feng    dma/hisilicon: use common PCI device naming
6be4c57add  Michael Baum     net/mlx5: fix errno update in shared context creation
dcbaafdc8f  Michael Baum     net/mlx5: fix sibling device config check
a501609ea6  Pablo de Lara    crypto/ipsec_mb: fix length and offset settings

^ permalink raw reply	[flat|nested] 7+ messages in thread
* please help backporting some patches to stable release 20.11.5
@ 2022-02-18 12:51 luca.boccassi
  0 siblings, 0 replies; 7+ messages in thread
From: luca.boccassi @ 2022-02-18 12:51 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 02/25/22.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 20.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 20.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 20.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
eb11edd9db  Alexander Kozyrev net/mlx5: fix meter capabilities reporting
728b6447e7  Alexander Kozyrev net/mlx5: fix MPRQ WQE size assertion
15174c40b7  Heinrich Kuhn    net/nfp: free HW ring memzone on queue release
5a2b22b40f  Huisong Li       net/hns3: fix mailbox wait time
2e1ecb460d  Jiawen Wu        net/txgbe: fix link up and down
10599cf83e  Michael Baum     common/mlx5: add minimum WQE size for striding RQ
8928997a13  Michael Baum     common/mlx5: fix error handling in multi-class probe
147f6fb42b  Michael Baum     net/mlx5: fix memory socket selection in ASO management
34776af600  Michael Baum     net/mlx5: fix MPRQ stride devargs adjustment
0947ed380f  Michael Baum     net/mlx5: improve stride parameter names
96c33cfb06  Min Hu (Connor)  net/hns3: fix Rx/Tx functions update
9cc217a283  Ruifeng Wang     config: add arch define for Arm

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2022-03-15 13:33 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-15 13:33 please help backporting some patches to stable release 20.11.5 luca.boccassi
  -- strict thread matches above, loose matches on Subject: below --
2022-03-09 16:38 luca.boccassi
2022-02-28 21:31 luca.boccassi
     [not found] ` <20220228213154.3344354-1-luca.boccassi@gmail.com>
2022-03-08 17:40   ` De Lara Guarch, Pablo
2022-03-09  0:13     ` Luca Boccassi
2022-03-14 11:07       ` De Lara Guarch, Pablo
2022-02-18 12:51 luca.boccassi

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).