From: "Power, Ciara" <ciara.power@intel.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 20.11.10
Date: Tue, 21 Nov 2023 14:23:37 +0000 [thread overview]
Message-ID: <SN7PR11MB7639F145D530B1F720205C38E6BBA@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231115114655.2355923-1-luca.boccassi@gmail.com>
Hi Luca,
> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Wednesday, November 15, 2023 11:47 AM
> To: dpdk stable <stable@dpdk.org>
> Cc: Akhil Goyal <gakhil@marvell.com>; Ashish Gupta
> <ashish.gupta@caviumnetworks.com>; Power, Ciara
> <ciara.power@intel.com>; Doherty, Declan <declan.doherty@intel.com>; Fan
> Zhang <roy.fan.zhang@intel.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; Ji, Kai <kai.ji@intel.com>; Shally Verma
> <shally.verma@caviumnetworks.com>; Sunila Sahu
> <sunila.sahu@caviumnetworks.com>
> Subject: please help backporting some patches to stable release 20.11.10
>
> 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 20.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 20.11 branch, or
> - Indicate that the patch should not be backported
>
> Please do either of the above by 2023/11/22.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.10
> release at:
> https://github.com/bluca/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 20.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
> --subject-prefix='PATCH 20.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 20.11 is located at tree:
> https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 47a85dda3f Ciara Power crypto/openssl: fix memory leaks in asym session
This one doesn't need to be backported to 20.11 - it relates to OpenSSL 3 specific code which wasn't supported in that release.
> 9d91c3047d Gowrishankar Muthukrishnan crypto/openssl: fix memory leaks
> in asym operations
next prev parent reply other threads:[~2023-11-21 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 11:46 luca.boccassi
2023-11-21 14:23 ` Power, Ciara [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-29 2:33 luca.boccassi
2023-12-01 3:21 ` huangdengdui
2023-11-08 19:28 luca.boccassi
2023-10-19 0:02 luca.boccassi
2023-10-19 0:23 ` Long Li
2023-10-23 9:38 ` Richardson, Bruce
2024-03-25 13:33 ` Chris Brezovec (cbrezove)
2024-03-25 13:55 ` Richardson, Bruce
2024-03-25 14:27 ` Luca Boccassi
2024-03-26 15:09 ` Richardson, Bruce
2024-03-26 18:57 ` Chris Brezovec (cbrezove)
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=SN7PR11MB7639F145D530B1F720205C38E6BBA@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=luca.boccassi@gmail.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).