patches for DPDK stable branches
 help / color / mirror / Atom feed
From: oulijun <oulijun@huawei.com>
To: <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.6
Date: Tue, 3 Nov 2020 17:06:48 +0800	[thread overview]
Message-ID: <ce6bb58c-841d-d4ba-23d5-6f906e7b28b0@huawei.com> (raw)
In-Reply-To: <20201102194342.1910626-1-luca.boccassi@gmail.com>


在 2020/11/3 3:43, luca.boccassi@gmail.com 写道:
> 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 2020/11/04.
> 
> 
> 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@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 19.11 is located at tree:
>     https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> 0134a5c7b4  Chengchang Tang  net/hns3: fix crash when Tx multiple buffer packets
Hi, Luca
   The fix(0134a5c7b4) is not applicable for 19.11. The 19.11 is not 
occur for this bug. Please ignore it

Thanks
Lijun Ou
> ce8628c66a  Harman Kalra     net/octeontx2: fix jumbo frame crash
> 9f6dc8592d  Huisong Li       ethdev: fix data type in TC queues
> 99ad2abc02  Kalesh AP        net/bnxt: fix speed setting on certain adapters
> c4ae7adafa  Kalesh AP        net/bnxt: fix UDP tunnel port removal
> 8410c369b4  Marvin Liu       net/virtio: fix indirect desc length
> b473061b0e  Marvin Liu       net/virtio: fix indirect descriptors in packed datapaths
> 93fa67fb11  Michael Baum     net/mlx5: fix Rx hash queue creation error flow
> c902e264f6  Michael Baum     net/mlx5: fix types differentiation in Rx queue create
> 227f283599  Pavan Nikhilesh  event/octeontx: validate events requested against available
> 059a231080  Phil Yang        app/testpmd: enable burst stats for noisy VNF mode
> 6b78a62995  Rahul Lakkireddy net/cxgbe: fix queue DMA ring leaks during port close
> 0f9ac2afa6  Sarosh Arif      common/octeontx2: fix memory mapping API usage
> 26cf65b23d  Shougang Wang    net/ice: fix firmware version output
> ef10add374  Venkat Duvvuru   net/bnxt: fix PF support in SR-IOV mode
> 0c87a15f5f  Xiaoyun Wang     net/hinic: fix filters on memory allocation failure
> 19cc028345  Xiaoyun Wang     net/hinic: fix TCAM filter set
> c21e5facf7  Xueming Li       net/mlx5: use bond index for netdev operations
> 9fb9a94caf  Yunjian Wang     net/bnxt: fix memory leak when freeing VF info
> .
> 

  reply	other threads:[~2020-11-03  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201102194256.1910550-1-luca.boccassi@gmail.com>
2020-11-02 19:43 ` luca.boccassi
2020-11-03  9:06   ` oulijun [this message]
2020-11-03 15:04 ` Ruifeng Wang
2020-11-04  8:42 ` Wangxiaoyun (Cloud)
2020-11-09 19:05 luca.boccassi
     [not found] ` <20201109190556.3481033-1-luca.boccassi@gmail.com>
2020-11-12  9:19   ` Fu, Patrick
2020-11-12  9:38     ` Luca Boccassi
2020-11-23  1:53   ` oulijun
2020-11-17 11:28 luca.boccassi
2020-11-25  9:07 luca.boccassi

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=ce6bb58c-841d-d4ba-23d5-6f906e7b28b0@huawei.com \
    --to=oulijun@huawei.com \
    --cc=stable@dpdk.org \
    /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).