[EXTERNAL] please help backporting some patches to stable release 22.11.9

[Rajesh Mudimadugula [C]]

Hi Luca,

9843181aa5  Rajesh Mudimadugula crypto/virtio: fix driver ID
Above need not be backported to 22.11

Thanks,
Rajesh.M

From: luca.boccassi at gmail.com <luca.boccassi at gmail.com>
Sent: Friday, June 13, 2025 2:46 AM
To: dpdk stable <stable at dpdk.org>
Cc: Akhil Goyal <gakhil at marvell.com>; Alejandro Lucero <alejandro.lucero at netronome.com>; Chaoyong He <chaoyong.he at corigine.com>; David Marchand <david.marchand at redhat.com>; Dengdui Huang <huangdengdui at huawei.com>; Dongdong Liu <liudongdong3 at huawei.com>; Fan Zhang <fanzhang.oss at gmail.com>; Hailin Xu <hailinx.xu at intel.com>; Huisong Li <lihuisong at huawei.com>; Jay Zhou <jianjay.zhou at huawei.com>; Jerin Jacob <jerinj at marvell.com>; Jie Hai <haijie1 at huawei.com>; Kaiwen Deng <kaiwenx.deng at intel.com>; Kiran Kumar Kokkilagadda <kirankumark at marvell.com>; Long Wu <long.wu at corigine.com>; Min Hu (Connor) <humin29 at huawei.com>; Niklas Söderlund <niklas.soderlund at corigine.com>; Nithin Kumar Dabilpuram <ndabilpuram at marvell.com>; Pavan Nikhilesh Bhagavatula <pbhagavatula at marvell.com>; Peng Zhang <peng.zhang at corigine.com>; Rajesh Mudimadugula [C] <rmudimadugul at marvell.com>; Rolf Neugebauer <rolf.neugebauer at netronome.com>; Ruifeng Wang <ruifeng.wang at arm.com>; Satha Koteswara Rao Kottidi <skoteshwar at marvell.com>; Shijith Thotton <sthotton at marvell.com>; Sunil Kumar Kori <skori at marvell.com>; Wei Hu (Xavier) <xavier.huwei at huawei.com>; Wei Zhao <wei.zhao1 at intel.com>; Wenzhuo Lu <wenzhuo.lu at intel.com>; Yisen Zhuang <yisen.zhuang at huawei.com>
Subject: [EXTERNAL] please help backporting some patches to stable release 22.11.9

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 22. 11 stable branch, as conflicts or build errors occur. Can authors check
ZjQcmQRYFpfptBannerStart
Prioritize security for external emails:
Confirm sender and content safety before clicking links or opening attachments
    Report Suspicious  <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/CRVmXkqW!tm3Z1f8UAnUa1E_8mf36zwiwFkFgixWLO_hng6RLQeOW-KlgbIi5czrWV8MtSjhe6yT7w5aLTn3Da67-l4wdWYtNktnmJacZ1c4KoA8$>   ‌
ZjQcmQRYFpfptBannerEnd

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 22.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 22.11 branch, or

    - Indicate that the patch should not be backported



Please do either of the above by 06/19/25.



You can find the a temporary work-in-progress branch of the coming 22.11.9

release at:

    https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_bluca_dpdk-2Dstable&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=rlAbIx8LaxcctFbwsUrAmdQNWj5VhDZR2BUJcFrO4iU&m=WOuU_2mv1KzP2-eYLmNiShcmILtZbC9CvL2Y6J7nqLY9CLxlhXygvMc-581JBmTD&s=j1V8IrXZQ2YeHciQ815MrefzhyfPCLK9rDA0_l_w8Mg&e=

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://urldefense.proofpoint.com/v2/url?u=https-3A__git.dpdk.org_dpdk-2Dstable_commit_-3Fh-3D18.11-26id-3Dd90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=rlAbIx8LaxcctFbwsUrAmdQNWj5VhDZR2BUJcFrO4iU&m=WOuU_2mv1KzP2-eYLmNiShcmILtZbC9CvL2Y6J7nqLY9CLxlhXygvMc-581JBmTD&s=tvu9T2ff0xSI_e-g6bSlQkkTrjtBqmVGitSR-nUb77w&e=



When sending the backported patch, please indicate the target branch in the

subject line, as we have multiple branches, for example:

    [PATCH 22.11] foo/bar: fix baz



With git format-patch, this can be achieved by appending the parameter:

    --subject-prefix='PATCH 22.11'



Send the backported patch to "stable at dpdk.org<mailto:stable at dpdk.org>" but not "dev at dpdk.org<mailto:dev at dpdk.org>".



FYI, branch 22.11 is located at tree:

   https://urldefense.proofpoint.com/v2/url?u=https-3A__git.dpdk.org_dpdk-2Dstable&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=rlAbIx8LaxcctFbwsUrAmdQNWj5VhDZR2BUJcFrO4iU&m=WOuU_2mv1KzP2-eYLmNiShcmILtZbC9CvL2Y6J7nqLY9CLxlhXygvMc-581JBmTD&s=EhM3IDXQQCitOntPHxcUJydnCR77JETebaOvZdhx8gU&e=



Thanks.



Luca Boccassi



---

53df26286e  Chaoyong He      net/nfp: fix crash with null RSS hash key

346a007e16  Chaoyong He      net/nfp: fix hash key length logic

7c37826c2b  David Marchand   test/lcore: fix race in per-lcore test

99c065da47  Dengdui Huang    net/hns3: fix Rx packet without CRC data

09766f41b3  Kaiwen Deng      net/ixgbe: enable ethertype filter for E610

98cf04bb90  Kiran Kumar K    test/graph: fix second run

f77eb8f3c6  Pavan Nikhilesh  event/cnxk: fix missing HW state checks

9843181aa5  Rajesh Mudimadugula crypto/virtio: fix driver ID

25e35296b5  Sunil Kumar Kori net/cnxk: fix reconfiguring MAC address
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/stable/attachments/20250617/17f0790f/attachment.htm>