patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Abdullah Sevincer" <abdullah.sevincer@intel.com>,
	"Alejandro Lucero" <alejandro.lucero@netronome.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Chaoyong He" <chaoyong.he@corigine.com>,
	"Chenbo Xia" <chenbo.xia@intel.com>,
	"Chengchang Tang" <tangchengchang@huawei.com>,
	"Chengwen Feng" <fengchengwen@huawei.com>,
	"Chunsong Feng" <fengchunsong@huawei.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Dengdui Huang" <huangdengdui@huawei.com>,
	"Ferruh Yigit" <ferruh.yigit@intel.com>,
	"Gage Eads" <gage.eads@intel.com>,
	"Hao Chen" <chenhao164@huawei.com>,
	"Heinrich Kuhn" <heinrich.kuhn@netronome.com>,
	"Hongbo Zheng" <zhenghongbo3@huawei.com>,
	"Huisong Li" <lihuisong@huawei.com>,
	"Jan Viktorin" <viktorin@rehivetech.com>,
	"Jerin Jacob" <jerinj@marvell.com>,
	"Jie Hai" <haijie1@huawei.com>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"Lijun Ou" <oulijun@huawei.com>, "Long Wu" <long.wu@corigine.com>,
	"Maxime Coquelin" <maxime.coquelin@redhat.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	"Neil Horman" <nhorman@tuxdriver.com>,
	"Patrick Fu" <patrick.fu@intel.com>,
	"Paul Szczepanek" <paul.szczepanek@arm.com>,
	"Peng Zhang" <peng.zhang@corigine.com>,
	"Ray Kinsella" <mdr@ashroe.eu>,
	"Rolf Neugebauer" <rolf.neugebauer@netronome.com>,
	"Ruifeng Wang" <ruifeng.wang@arm.com>,
	"Timothy McDaniel" <timothy.mcdaniel@intel.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"Yisen Zhuang" <yisen.zhuang@huawei.com>
Subject: please help backporting some patches to stable release 20.11.10
Date: Wed,  8 Nov 2023 19:28:24 +0000	[thread overview]
Message-ID: <20231108192824.923290-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/11/15.

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

---
1e80c07472  Chaoyong He      net/nfp: fix reconfigure logic in PF initialization
d67022275d  Chaoyong He      net/nfp: fix reconfigure logic of set MAC address
1eee1ea75c  Dengdui Huang    net/hns3: fix IMP or global reset
5be38fc6c0  Dengdui Huang    net/hns3: fix multiple reset detected log
c01ffb24a2  Dengdui Huang    net/hns3: refactor interrupt state query
a4b2c6815a  Huisong Li       net/hns3: fix LRO offload to report
7bfb0d4eaf  Juraj Linkeš     config/arm: fix aarch32 build with GCC 13
867d31bed4  Maxime Coquelin  vhost: fix check on virtqueue access in async registration

             reply	other threads:[~2023-11-08 19:28 UTC|newest]

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

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=20231108192824.923290-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=abdullah.sevincer@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=bruce.richardson@intel.com \
    --cc=chaoyong.he@corigine.com \
    --cc=chenbo.xia@intel.com \
    --cc=chenhao164@huawei.com \
    --cc=david.marchand@redhat.com \
    --cc=fengchengwen@huawei.com \
    --cc=fengchunsong@huawei.com \
    --cc=ferruh.yigit@intel.com \
    --cc=gage.eads@intel.com \
    --cc=haijie1@huawei.com \
    --cc=heinrich.kuhn@netronome.com \
    --cc=huangdengdui@huawei.com \
    --cc=humin29@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lihuisong@huawei.com \
    --cc=long.wu@corigine.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdr@ashroe.eu \
    --cc=nhorman@tuxdriver.com \
    --cc=oulijun@huawei.com \
    --cc=patrick.fu@intel.com \
    --cc=paul.szczepanek@arm.com \
    --cc=peng.zhang@corigine.com \
    --cc=rolf.neugebauer@netronome.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stable@dpdk.org \
    --cc=tangchengchang@huawei.com \
    --cc=timothy.mcdaniel@intel.com \
    --cc=viktorin@rehivetech.com \
    --cc=xavier.huwei@huawei.com \
    --cc=yisen.zhuang@huawei.com \
    --cc=zhenghongbo3@huawei.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).