Re: please help backporting some patches to stable release 24.11.3

[Kevin Traynor <ktraynor@redhat.com>]

On 21/07/2025 17:36, Richardson, Bruce wrote:
> I don't see any build errors with 24.11 branch on freebsd, so I think no backport of b4ce09b852   is necessary.
> 
> For 4cd8c72f66, I would also hold off in backporting, as I'm afraid of it possibly breaking something. More fixes are likely needed in that driver area in 25.11, so I would reconsider it only after that has all settled down.
> 

Ok Bruce, thanks for confirming.
Kevin.

> /Bruce
> 
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Monday, July 21, 2025 5:06 PM
>> To: dpdk stable <stable@dpdk.org>
>> Cc: Akhil Goyal <gakhil@marvell.com>; Burakov, Anatoly
>> <anatoly.burakov@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>;
>> Dengdui Huang <huangdengdui@huawei.com>; Huisong Li
>> <lihuisong@huawei.com>; Jerin Jacob <jerinj@marvell.com>; Jie Hai
>> <haijie1@huawei.com>; Kiran Kumar K <kirankumark@marvell.com>; Nithin
>> Dabilpuram <ndabilpuram@marvell.com>; Nithinsen Kaithakadan
>> <nkaithakadan@marvell.com>; Rajesh Mudimadugula
>> <rmudimadugul@marvell.com>; Sunil Kumar Kori <skori@marvell.com>; Tejasree
>> Kondoj <ktejasree@marvell.com>
>> Subject: please help backporting some patches to stable release 24.11.3
>>
>> 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 24.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 24.11 branch, or
>>     - Indicate that the patch should not be backported
>>
>> Please do either of the above by 07/28/25.
>>
>> You can find the a temporary work-in-progress branch of the coming 24.11.3
>> release at:
>>     https://github.com/kevintraynor/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 24.11] foo/bar: fix baz
>>
>> With git format-patch, this can be achieved by appending the parameter:
>>     --subject-prefix='PATCH 24.11'
>>
>> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>>
>> FYI, branch 24.11 is located at tree:
>>    https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
>> b4ce09b852  Bruce Richardson net/ixgbe/base: fix lock checker errors
>> 25e35296b5  Sunil Kumar Kori net/cnxk: fix reconfiguring MAC address
>> 9843181aa5  Rajesh Mudimadugula crypto/virtio: fix driver ID
>> a1efd31b0f  Nithinsen Kaithakadan common/cnxk: fix AES-CTR salt handling
>> 99c065da47  Dengdui Huang    net/hns3: fix Rx packet without CRC data
>> 98cf04bb90  Kiran Kumar K    test/graph: fix second run
>> 4cd8c72f66  Bruce Richardson net/ice: fix inconsistency in Rx queue VLAN tag
>> placement (struct ci_rx_queue does not exist in 24.11)
>