patches for DPDK stable branches
 help / color / Atom feed
From: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>
To: Luca Boccassi <bluca@debian.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.3
Date: Fri, 29 May 2020 11:38:02 +0800
Message-ID: <9268f584-67a7-8030-78df-6a3530897762@huawei.com> (raw)
In-Reply-To: <ef8286ce8503931cbc79303d55a592565c586ac5.camel@debian.org>

Hi,  Luca Boccassi


On 2020/5/29 0:35, Luca Boccassi wrote:
> On Thu, 2020-05-28 at 17:29 +0800, Wei Hu (Xavier) wrote:
>> Hi,  Luca Boccassi
>>
>> On 2020/5/27 18:14, luca.boccassi@gmail.com wrote:
>>> Hi commit authors (and maintainers),
>>>
>>> I didn't apply following commits from DPDK master 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 June the 3rd.
>>>
>>>
>>> Some notes on stable backports:
>>>
>>> A backport should contain a reference to the DPDK master branch commit
>>> in it's commit message in 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 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
>>>
>>> ---
>>> 96477b5dd5  Ajit Khaparde    net/bnxt: fix allocation of COS queue info
>>> 205b742952  Ajit Khaparde    net/bnxt: fix allocation of LED config info
>>> 986fa3ba83  Ajit Khaparde    net/bnxt: fix allocation of link info struct
>>> e8fe0e067b  Ajit Khaparde    net/bnxt: fix allocation of PF info struct
>>> 29fdc5bf45  Apeksha Gupta    test/crypto: fix statistics case
>>> fb94f35948  Chengchang Tang  net/hns3: fix adding multicast MAC address
>> DPDK19.11 is the first version of the hns3 driver integrated into the DPDK.
>> In this version, the features based on hns3 network engine are not complete,
>> we prefer to recommend users to use the updated version.
>>
>> "fb94f35948 Chengchang Tang net/hns3: fix adding multicast MAC address"
>> For the above patch, we think that it will have little effect if this patch
>> does not merged into the 19.11.x version.
>>> a4e6ea97a5  Dekel Peled      common/mlx5: fix RSS key copy to TIR context
>>> 1db72630da  Dmitry Kozlyuk   eal/windows: do not expose private facilities
>>> 867b49d17a  Ferruh Yigit     ring: fix build for gcc O1 optimization
>>> 48f9faddc6  Kalesh AP        net/bnxt: fix MAC address setting when port is stopped
>>> 10d6982008  Kalesh AP        net/bnxt: fix recovery alarm race condition in port close
>>> 920be799db  Lijun Ou         net/hns3: fix RSS indirection table configuration
>> "920be799db Lijun Ou net/hns3: fix RSS indirection table configuration"
>> This patch depends on the following patch:
>>       "a951c1ed3 net/hns3: support different numbers of Rx and Tx queues",
>> but the patch was accepted in dpdk20.02.0, not merged in dpdk 19.11.x.
>> Can you give some suggestions?
> a951c1ed3 does not apply cleanly either. If you'd like to have both in
> 19.11.3, please backport them both on top of dpdk-stable/19.11 and send
> them to stable@dpdk.org. If you don't think it's worth having them,
> that's fine too.
> .
Thanks. I will send the related patches as soon as possible.

     Regards
Xavier
>


  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200527101401.274945-1-luca.boccassi@gmail.com>
2020-05-28  9:29 ` Wei Hu (Xavier)
2020-05-28 16:35   ` Luca Boccassi
2020-05-29  3:38     ` Wei Hu (Xavier) [this message]
2020-06-05 12:49 ` Ferruh Yigit
2020-05-27 16:10 Luca Boccassi
2020-06-03  8:48 ` Luca Boccassi

Reply instructions:

You may reply publically 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=9268f584-67a7-8030-78df-6a3530897762@huawei.com \
    --to=xavier.huwei@huawei.com \
    --cc=bluca@debian.org \
    --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

patches for DPDK stable branches

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/ public-inbox