patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Richael Zhuang <Richael.Zhuang@arm.com>, dpdk stable <stable@dpdk.org>
Cc: nd <nd@arm.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 20.11.3
Date: Fri, 16 Jul 2021 10:50:20 +0100	[thread overview]
Message-ID: <8b7b785813106a708f37f9a0c8fef87fc9737a7e.camel@debian.org> (raw)
In-Reply-To: <AM8PR08MB57960534EFAC448A638BE45792119@AM8PR08MB5796.eurprd08.prod.outlook.com>

On Fri, 2021-07-16 at 06:12 +0000, Richael Zhuang wrote:
> Hi,
> This patch
> "29343b9030  Richael Zhuang   test/power: fix CPU frequency when turbo enabled" should not be backport. It's based on commit ef1cc88f1837 and  06cffd468fd.
> 
> Best Regards,
> Richael

Ok, thanks.

> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Thursday, July 15, 2021 11:05 PM
> > Cc: Ajit Khaparde (ajit.khaparde@broadcom.com)
> > <ajit.khaparde@broadcom.com>; Churchill Khangar
> > <churchill.khangar@intel.com>; Cristian Dumitrescu
> > <cristian.dumitrescu@intel.com>; David Christensen
> > <david.christensen@broadcom.com>; David Hunt <david.hunt@intel.com>;
> > Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>; Jie Zhou <jizh@microsoft.com>;
> > Matan Azrad <matan@nvidia.com>; Narcisa Vasile
> > <navasile@linux.microsoft.com>; Ori Kam <orika@nvidia.com>; Pallavi
> > Kadam <pallavi.kadam@intel.com>; Ranjit Menon
> > <ranjit.menon@intel.com>; Richael Zhuang <Richael.Zhuang@arm.com>;
> > Shahaf Shuler <shahafs@nvidia.com>; Somnath Kotur
> > <somnath.kotur@broadcom.com>; Steeven Li <steeven.li@broadcom.com>;
> > Stephen Hurd <stephen.hurd@broadcom.com>; Tyler Retzlaff
> > <roretzla@linux.microsoft.com>; Venkata Suresh Kumar P
> > <venkata.suresh.kumar.p@intel.com>; Viacheslav Ovsiienko
> > <viacheslavo@nvidia.com>
> > Subject: please help backporting some patches to stable release 20.11.3
> > 
> > Hi commit authors (and maintainers),
> > 
> > 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 07/22/21.
> > 
> > You can find the a temporary work-in-progress branch of the coming 20.11.3
> > 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
> > 
> > ---
> > b3fa83945a  Ajit Khaparde    net/bnxt: fix ring allocation and free
> > a57d92d73d  Cristian Dumitrescu pipeline: fix table entry read
> > cfdaa678b3  Dmitry Kozlyuk   eal/windows: cleanup interrupt resources
> > 3888f31950  Dmitry Kozlyuk   eal/windows: fix interrupt thread handle
> > leakage
> > 35dff5d3b7  Dmitry Kozlyuk   eal/windows: fix interrupt thread ID
> > 29343b9030  Richael Zhuang   test/power: fix CPU frequency when turbo
> > enabled
> > 03c8f2fe11  Somnath Kotur    net/bnxt: detect bad opaque in Rx completion
> > c150dff40d  Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format


  reply	other threads:[~2021-07-16  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 15:04 luca.boccassi
2021-07-16  6:33 ` Somnath Kotur
     [not found] ` <20210715150520.2731947-1-luca.boccassi@gmail.com>
2021-07-16  6:12   ` Richael Zhuang
2021-07-16  9:50     ` Luca Boccassi [this message]
2021-07-20 15:26   ` Slava Ovsiienko
2021-07-21 12:10     ` Luca Boccassi
2021-07-26 14:41 luca.boccassi

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=8b7b785813106a708f37f9a0c8fef87fc9737a7e.camel@debian.org \
    --to=bluca@debian.org \
    --cc=Richael.Zhuang@arm.com \
    --cc=nd@arm.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).