patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Bernard Iremonger <bernard.iremonger@intel.com>,
	Chengchang Tang <tangchengchang@huawei.com>,
	Chengwen Feng <fengchengwen@huawei.com>,
	Chunsong Feng <fengchunsong@huawei.com>,
	Dmitry Kozlyuk <dkozlyuk@nvidia.com>,
	Dongdong Liu <liudongdong3@huawei.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Gerry Gribbon <ggribbon@nvidia.com>,
	Hao Chen <chenhao164@huawei.com>,
	Huisong Li <lihuisong@huawei.com>, Lijun Ou <oulijun@huawei.com>,
	Matan Azrad <matan@nvidia.com>,
	Michael Baum <michaelba@nvidia.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Ori Kam <orika@nvidia.com>, Shahaf Shuler <shahafs@nvidia.com>,
	Shiyang He <shiyangx.he@intel.com>,
	Tal Shnaiderman <talshn@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Yisen Zhuang <yisen.zhuang@huawei.com>
Subject: please help backporting some patches to stable release 20.11.8
Date: Wed, 15 Mar 2023 22:49:09 +0000	[thread overview]
Message-ID: <20230315224909.1026727-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 22/03/23.

You can find the a temporary work-in-progress branch of the coming 20.11.8
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

---
8e9bd29995  Chengwen Feng    net/hns3: fix empty devargs parsing
b15d75b287  Gerry Gribbon    regex/mlx5: fix doorbell record
eb3ef9e0d7  Huisong Li       net/hns3: add verification of RSS types
e3069658da  Huisong Li       net/hns3: reimplement hash flow function
5028f207a4  Shiyang He       app/testpmd: fix secondary process packet forwarding

             reply	other threads:[~2023-03-15 22:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 22:49 luca.boccassi [this message]
2023-03-21  9:37 ` lihuisong (C)
  -- strict thread matches above, loose matches on Subject: below --
2023-03-29  1:05 luca.boccassi
2023-03-22  0:43 luca.boccassi
2023-02-23  9:42 luca.boccassi
2023-03-01 16:15 ` Kundapura, Ganapati
2023-03-02  9:47   ` Luca Boccassi
2023-03-02 10:18     ` Kundapura, Ganapati
2023-03-21  9:29 ` lihuisong (C)

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=20230315224909.1026727-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=chenhao164@huawei.com \
    --cc=dkozlyuk@nvidia.com \
    --cc=fengchengwen@huawei.com \
    --cc=fengchunsong@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=ferruh.yigit@intel.com \
    --cc=ggribbon@nvidia.com \
    --cc=humin29@huawei.com \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=oulijun@huawei.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=shahafs@nvidia.com \
    --cc=shiyangx.he@intel.com \
    --cc=stable@dpdk.org \
    --cc=talshn@nvidia.com \
    --cc=tangchengchang@huawei.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xavier.huwei@huawei.com \
    --cc=yisen.zhuang@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).