patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
Cc: dpdk stable <stable@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	"Beilei Xing" <beilei.xing@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	 Chandubabu Namburu <chandu@amd.com>,
	Chenbo Xia <chenbo.xia@intel.com>,
	Chengwen Feng <fengchengwen@huawei.com>,
	David Marchand <david.marchand@redhat.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	"Ferruh Yigit" <ferruh.yigit@intel.com>,
	Harman Kalra <hkalra@marvell.com>,
	"Jerin Jacob" <jerinj@marvell.com>, Jie Hai <haijie1@huawei.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
	Leyi Rong <leyi.rong@intel.com>, Lijun Ou <oulijun@huawei.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Mingxia Liu <mingxia.liu@intel.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	"Qi Zhang" <qi.z.zhang@intel.com>,
	Radha Mohan Chintakuntla <radhac@marvell.com>,
	 Sampath Peechu <speechu@cisco.com>,
	Satha Rao <skoteshwar@marvell.com>,
	"Sunil Kumar Kori" <skori@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Vamsi Attunuru" <vattunuru@marvell.com>,
	Veerasenareddy Burru <vburru@marvell.com>,
	Vidya Sagar Velumuri <vvelumuri@marvell.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Zhimin Huang <zhiminx.huang@intel.com>
Subject: please help backporting some patches to stable release 22.11.4
Date: Sun, 22 Oct 2023 22:50:08 +0800	[thread overview]
Message-ID: <20231022145008.16706-1-xuemingl@nvidia.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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 11/15/23.

You can find the a temporary work-in-progress branch of the coming 22.11.4
release at:
    https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
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 22.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 22.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 22.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Xueming Li <xuemingl@nvidia.com>

---
4f6f36ce23  Akhil Goyal      common/cnxk: fix leak in error path
b47f378539  Akhil Goyal      net/cnxk: fix usage of mbuf rearm data
ef12cbbee0  Beilei Xing      common/idpf: fix Tx checksum offload
12016895fc  Bruce Richardson net/iavf: fix buffer leak on Tx queue stop
0236016c02  Jie Hai          net/axgbe: fix Rx and Tx queue state
8c41645be0  Maxime Coquelin  net/virtio: fix descriptor addresses in 32-bit build
a6f639e079  Sunil Kumar Kori common/cnxk: fix BP threshold calculation
ba39a261a7  Vamsi Attunuru   dma/cnxk: fix completion ring tail wrap

                 reply	other threads:[~2023-10-22 14:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231022145008.16706-1-xuemingl@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chandu@amd.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=ferruh.yigit@intel.com \
    --cc=gakhil@marvell.com \
    --cc=haijie1@huawei.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=jingjing.wu@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=leyi.rong@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mingxia.liu@intel.com \
    --cc=ndabilpuram@marvell.com \
    --cc=oulijun@huawei.com \
    --cc=pbhagavatula@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=radhac@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=speechu@cisco.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.com \
    --cc=vburru@marvell.com \
    --cc=vvelumuri@marvell.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=zhiminx.huang@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).