patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 21.11.6
Date: Tue, 12 Dec 2023 09:52:21 +0000	[thread overview]
Message-ID: <SN7PR11MB7639D233140D86C5FB562A14E68EA@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231207113825.771708-1-ktraynor@redhat.com>



> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Thursday, December 7, 2023 11:38 AM
> To: dpdk stable <stable@dpdk.org>
> Cc: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; Akhil Goyal
> <gakhil@marvell.com>; Amit Prakash Shukla <amitprakashs@marvell.com>;
> Burakov, Anatoly <anatoly.burakov@intel.com>; Anoob Joseph
> <anoobj@marvell.com>; Ashwin Sekhar T K <asekhar@marvell.com>; Bing
> Zhao <bingz@nvidia.com>; Chaoyong He <chaoyong.he@corigine.com>;
> Power, Ciara <ciara.power@intel.com>; Walsh, Conor
> <conor.walsh@intel.com>; Marchand, David <david.marchand@redhat.com>;
> Ferruh Yigit <ferruh.yigit@amd.com>; Kundapura, Ganapati
> <ganapati.kundapura@intel.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; Hanumanth Pothula
> <hpothula@marvell.com>; Harman Kalra <hkalra@marvell.com>; Hemant
> Agrawal <hemant.agrawal@nxp.com>; Honnappa Nagarahalli
> <honnappa.nagarahalli@arm.com>; Jerin Jacob <jerinj@marvell.com>; Jiawen
> Wu <jiawenwu@trustnetic.com>; Jie Hai <haijie1@huawei.com>; Ji, Kai
> <kai.ji@intel.com>; Kaisen You <kaisenx.you@intel.com>; Deng, KaiwenX
> <kaiwenx.deng@intel.com>; Kiran Kumar K <kirankumark@marvell.com>;
> Matan Azrad <matan@nvidia.com>; Michael Baum <michaelba@nvidia.com>;
> Ye, MingjinX <mingjinx.ye@intel.com>; Mohammad Iqbal Ahmad
> <mahmad@marvell.com>; Morten Brørup <mb@smartsharesystems.com>;
> Nithin Dabilpuram <ndabilpuram@marvell.com>; Matz, Olivier
> <olivier.matz@6wind.com>; Ori Kam <orika@nvidia.com>; Pavan Nikhilesh
> <pbhagavatula@marvell.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Rahul
> Bhansali <rbhansali@marvell.com>; Ruifeng Wang <ruifeng.wang@arm.com>;
> Shijith Thotton <sthotton@marvell.com>; Srujana Challa
> <schalla@marvell.com>; Stephen Hemminger
> <stephen@networkplumber.org>; Steve Yang <stevex.yang@intel.com>;
> Suanming Mou <suanmingm@nvidia.com>; Sunil Kumar Kori
> <skori@marvell.com>; Tyler Retzlaff <roretzla@linux.microsoft.com>; Vamsi
> Attunuru <vattunuru@marvell.com>; Viacheslav Ovsiienko
> <viacheslavo@nvidia.com>
> Subject: please help backporting some patches to stable release 21.11.6
> 
> 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 21.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 21.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 12/12/23.
> 
> You can find the a temporary work-in-progress branch of the coming 21.11.6
> 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 21.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 21.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 21.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Kevin
> 
> ---
> 2e9863fbb6  Akhil Goyal      common/cnxk: fix different size bit operations
> 4f6f36ce23  Akhil Goyal      common/cnxk: fix leak in error path
> d2d7f0190b  Akhil Goyal      doc: fix code blocks in cryptodev guide
> 3dd3115078  Amit Prakash Shukla dma/cnxk: fix chunk buffer failure return
> code
> 95a955e3e0  Amit Prakash Shukla dma/cnxk: fix device reconfigure
> 63bf81a617  Anatoly Burakov  test: fix named test macro
> c5b531d6ee  Anoob Joseph     app/crypto-perf: fix session freeing
> 6df1bc6b3b  Ashwin Sekhar T K mempool/cnxk: avoid hang when counting
> batch allocs b3ddd649ad  Ashwin Sekhar T K mempool/cnxk: fix alloc from
> non-EAL threads
> 37ca457d3f  Bing Zhao        common/mlx5: fix obtaining IB device in LAG mode
> 2ece3b7186  Bing Zhao        net/mlx5: fix flow workspace double free in
> Windows
> 47a85dda3f  Ciara Power      crypto/openssl: fix memory leaks in asym session

Hi Kevin,

These fixes relate to Openssl 3 codepaths that didn't exist in 21.11.
Fix does not need backporting.

Thanks,
Ciara




  reply	other threads:[~2023-12-12  9:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 11:38 Kevin Traynor
2023-12-12  9:52 ` Power, Ciara [this message]
2023-12-14  9:23   ` Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2023-11-16 14:08 Kevin Traynor
2023-11-16 13:33 Kevin Traynor
2023-11-16 13:39 ` Kevin Traynor
2023-11-02 13:45 Kevin Traynor
2023-11-02 13:54 ` Richardson, Bruce
2023-11-03 21:11   ` Kevin Traynor
2023-11-03  3:09 ` Rongwei Liu
2023-11-06 16:11 ` Kishore Padmanabha
2023-11-07 13:02   ` Kevin Traynor
2023-11-09 12:24 ` Sebastian, Selwin
2023-11-09 12:58   ` Kevin Traynor

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=SN7PR11MB7639D233140D86C5FB562A14E68EA@SN7PR11MB7639.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=ktraynor@redhat.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).