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

luca.boccassi at gmail.com luca.boccassi at gmail.com
Wed Nov 25 10:07:29 CET 2020


Hi commit authors (and maintainers),

I didn't apply following commits from DPDK main to 19.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 19.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by November 30th.


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 19.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
023b46db54  Harman Kalra     common/octeontx2: fix mbox response by syncing data types
5ea8356ec8  Tonghao Zhang    net/mlx5: check register available for metadata action


More information about the stable mailing list