patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Long Li <longli@microsoft.com>
To: dpdk stable <stable@dpdk.org>,
	"luca.boccassi@gmail.com" <luca.boccassi@gmail.com>
Cc: Wei Hu <weh@microsoft.com>
Subject: RE: please help backporting some patches to stable release 20.11.10
Date: Thu, 19 Oct 2023 00:23:11 +0000	[thread overview]
Message-ID: <PH7PR21MB32633E16A5A7E24795C15A4ACED4A@PH7PR21MB3263.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20231019000255.3823-1-luca.boccassi@gmail.com>

Hi Luca,

The following patches should not be backported to stable 20.11.

> 26c6bdf3d1  Wei Hu           net/mana: add 32-bit short doorbell
> 74decf3bf0  Wei Hu           net/mana: enable 32-bit build

Thank you,

Long

> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Wednesday, October 18, 2023 5:03 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Abhijit Sinha <abhijit.sinha@intel.com>; Anatoly Burakov
> <anatoly.burakov@intel.com>; Beilei Xing <beilei.xing@intel.com>; Bernard
> Iremonger <bernard.iremonger@intel.com>; Bruce Richardson
> <bruce.richardson@intel.com>; Chandubabu Namburu <chandu@amd.com>;
> Ciara Power <ciara.power@intel.com>; Declan Doherty
> <declan.doherty@intel.com>; Deepak Kumar Jain <deepak.k.jain@intel.com>;
> Dmitry Kozlyuk <dkozlyuk@nvidia.com>; Ferruh Yigit
> <ferruh.yigit@amd.com>; Ferruh Yigit <ferruh.yigit@intel.com>; Fiona Trahe
> <fiona.trahe@intel.com>; Hernan Vargas <hernan.vargas@intel.com>; Jie Hai
> <haijie1@huawei.com>; Jingjing Wu <jingjing.wu@intel.com>; John Griffin
> <john.griffin@intel.com>; Konstantin Ananyev
> <konstantin.ananyev@intel.com>; Leyi Rong <leyi.rong@intel.com>; Long Li
> <longli@microsoft.com>; Matan Azrad <matan@nvidia.com>; Maxime
> Coquelin <maxime.coquelin@redhat.com>; Nicolas Chautru
> <nicolas.chautru@intel.com>; Qi Zhang <qi.z.zhang@intel.com>; Radu Nicolau
> <radu.nicolau@intel.com>; Saurabh Singhal <saurabhs@arista.com>; Selwin
> Sebastian <selwin.sebastian@amd.com>; Somalapuram Amaranath
> <asomalap@amd.com>; Thomas Monjalon <thomas@monjalon.net>; Wei Hu
> <weh@microsoft.com>; Wenzhuo Lu <wenzhuo.lu@intel.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/10/26.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.10
> release at:
>
> https://gith/
> ub.com%2Fbluca%2Fdpdk-
> stable&data=05%7C01%7Clongli%40microsoft.com%7C88692d1c42094f053
> 86b08dbd036c5d6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%
> 7C638332705966366690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wL
> jAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
> %7C%7C&sdata=sfCTswh8te9raFdLBSZoepSJDswS9XWW7f7c2e8Fzpg%3D&r
> eserved=0
> 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.d/
> pdk.org%2Fdpdk-
> stable%2Fcommit%2F%3Fh%3D18.11%26id%3Dd90e6ae6f936ecdc2fd3811
> ff9f26aec7f3c06eb&data=05%7C01%7Clongli%40microsoft.com%7C88692d
> 1c42094f05386b08dbd036c5d6%7C72f988bf86f141af91ab2d7cd011db47
> %7C1%7C0%7C638332705966374971%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C3000%7C%7C%7C&sdata=Op%2Ba2zXddKaac%2BnF8bte0jARsXL77HC%
> 2FrLks11%2FtT6g%3D&reserved=0
>
> 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.d/
> pdk.org%2Fdpdk-
> stable&data=05%7C01%7Clongli%40microsoft.com%7C88692d1c42094f053
> 86b08dbd036c5d6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%
> 7C638332705966383769%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wL
> jAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
> %7C%7C&sdata=xWKECUfWfEK5KC%2BF38LGtCckByCDQlYZUl0CV8qsKv8%3
> D&reserved=0
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 12016895fc  Bruce Richardson net/iavf: fix buffer leak on Tx queue stop
> d7d52b37e8  Ciara Power      crypto/qat: fix raw API null algorithm digest
> 7d04891664  Hernan Vargas    baseband/acc: fix ACC100 HARQ input
> alignment
> 37b68fa144  Jie Hai          app/testpmd: fix primary process not polling all
> queues
> e35a5737a7  Saurabh Singhal  net/iavf: unregister interrupt handler before FD
> close
> a27ff9cac1  Selwin Sebastian net/axgbe: identify CPU with cpuid
> 26c6bdf3d1  Wei Hu           net/mana: add 32-bit short doorbell
> 74decf3bf0  Wei Hu           net/mana: enable 32-bit build

  reply	other threads:[~2023-10-19  0:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  0:02 luca.boccassi
2023-10-19  0:23 ` Long Li [this message]
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)
2023-11-08 19:28 luca.boccassi
2023-11-15 11:46 luca.boccassi
2023-11-21 14:23 ` Power, Ciara
2023-11-29  2:33 luca.boccassi
2023-12-01  3:21 ` huangdengdui

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=PH7PR21MB32633E16A5A7E24795C15A4ACED4A@PH7PR21MB3263.namprd21.prod.outlook.com \
    --to=longli@microsoft.com \
    --cc=luca.boccassi@gmail.com \
    --cc=stable@dpdk.org \
    --cc=weh@microsoft.com \
    /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).