patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
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
Date: Thu, 19 Oct 2023 01:02:55 +0100	[thread overview]
Message-ID: <20231019000255.3823-1-luca.boccassi@gmail.com> (raw)

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://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

---
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:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  0:02 luca.boccassi [this message]
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)
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=20231019000255.3823-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=abhijit.sinha@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=asomalap@amd.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chandu@amd.com \
    --cc=ciara.power@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dkozlyuk@nvidia.com \
    --cc=ferruh.yigit@amd.com \
    --cc=ferruh.yigit@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=haijie1@huawei.com \
    --cc=hernan.vargas@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.griffin@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=leyi.rong@intel.com \
    --cc=longli@microsoft.com \
    --cc=matan@nvidia.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nicolas.chautru@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=saurabhs@arista.com \
    --cc=selwin.sebastian@amd.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=weh@microsoft.com \
    --cc=wenzhuo.lu@intel.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).