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

Somnath Kotur somnath.kotur at broadcom.com
Wed Mar 18 06:58:03 CET 2020


On Fri, Mar 6, 2020 at 10:23 PM Kevin Traynor <ktraynor at redhat.com> wrote:
>
> Hi commit authors (and maintainers),
>
> I didn't apply following commits from DPDK master to 18.11
> LTS branch, as conflicts or build errors occur. Note, it may be
> dependent on another patch below that has not been applied.
>
> Can authors check your patches in the following list and either:
>     - Backport your patches to the 18.11 branch, or
>     - Indicate that the patch should not be backported
>
> Please do either of the above by 03/13/20.
>
> Some notes on LTS backports:
>
> A backport should contain a reference to the DPDK master branch commit
> in it's commit message in exactly the following fashion:
>     [ upstream commit <commit's dpdk master 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 18.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 18.11'
>
> Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
>
> FYI, branch 18.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Kevin.
>
> ---
Hi Kevin,
            Only the following 4 bnxt patches will be needed, have
just sent the backported versions of these patches to stable at dpdk.org

 f35eaaca5  Stephen Hemminger net/bnxt: fix crash in secondary process
 d9fc6a0d0  Kalesh AP        net/bnxt: fix probe in FreeBSD
 8f3224f26  Kalesh AP        net/bnxt: fix IOVA mapping
 975ff25e7  Rahul Gupta      net/bnxt: fix default timeout for getting
FW version

Thanks a lot!

-Som


More information about the stable mailing list