patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: Daxue Gao <daxuex.gao@intel.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Rakesh Kudurumalla <rkudurumalla@marvell.com>,
	dpdk stable <stable@dpdk.org>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: RE: [EXT] please help backporting some patches to stable release 21.11.1
Date: Wed, 6 Apr 2022 06:31:01 +0000	[thread overview]
Message-ID: <CO1PR18MB4714FE64166E7CAF1646E2A1CBE79@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220405150610.204296-1-ktraynor@redhat.com>

Hi Kevin,
Please ignore below patch, as its correct parent patch is 8bdbae66b29 which is not
applicable for 21.11 lts.

315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks

Thanks for the heads up,
Gowrishankar

> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Tuesday, April 5, 2022 8:36 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Daxue Gao <daxuex.gao@intel.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>; Rakesh Kudurumalla <rkudurumalla@marvell.com>
> Subject: [EXT] please help backporting some patches to stable release
> 21.11.1
> 
> External Email
> 
> ----------------------------------------------------------------------
> 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 04/08/22.
> 
> 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=nKjWec2b6R
> 0mOyPaz7xtfQ&r=EAtr-
> g7yUFhtOio8r2Rtm13Aqe4WVp_S_gHpcu6KFVo&m=j0EyEihXoey-
> V3LVeQLzaLP5yIQ7UnoyOsjyugbqwqhQsqLAY2MLuJDQV1FYIrqz&s=CiXClXhR
> XUM0MWZeczFG8POC1BSsmRnnAhJqC4X4GmU&e=
> 
> 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__git.dpdk.org_dpdk-
> 2Dstable&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=EAtr-
> g7yUFhtOio8r2Rtm13Aqe4WVp_S_gHpcu6KFVo&m=j0EyEihXoey-
> V3LVeQLzaLP5yIQ7UnoyOsjyugbqwqhQsqLAY2MLuJDQV1FYIrqz&s=gPt7G2A
> NGvpHDNUkA15_3PSCZ3A1VQPx3zEyUKCuApQ&e=
> 
> Thanks.
> 
> Kevin
> 
> ---
> 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
> 68f8a52a6b  Rakesh Kudurumalla net/cnxk: fix build with optimization


  reply	other threads:[~2022-04-06  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 15:06 Kevin Traynor
2022-04-06  6:31 ` Gowrishankar Muthukrishnan [this message]
2022-04-06  9:39   ` [EXT] " 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=CO1PR18MB4714FE64166E7CAF1646E2A1CBE79@CO1PR18MB4714.namprd18.prod.outlook.com \
    --to=gmuthukrishn@marvell.com \
    --cc=daxuex.gao@intel.com \
    --cc=jerinj@marvell.com \
    --cc=ktraynor@redhat.com \
    --cc=pbhagavatula@marvell.com \
    --cc=rkudurumalla@marvell.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).