patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Benjamin Le Berre <benjamin.le_berre@6wind.com>
To: dpdk stable <stable@dpdk.org>
Cc: "Abdullah Ömer Yamaç" <omer.yamac@ceng.metu.edu.tr>,
	"Ajit Khaparde" <ajit.khaparde@broadcom.com>,
	"Akhil Goyal" <gakhil@marvell.com>,
	"Alexander Kozyrev" <akozyrev@nvidia.com>,
	"Alice Michael" <alice.michael@intel.com>,
	"Andy Gospodarek" <andrew.gospodarek@broadcom.com>,
	"Anirudh Venkataramanan" <anirudh.venkataramanan@intel.com>,
	"Beilei Xing" <beilei.xing@intel.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Chenbo Xia" <chenbo.xia@intel.com>,
	"Chunsong Feng" <fengchunsong@huawei.com>,
	"Damodharam Ammepalli" <damodharam.ammepalli@broadcom.com>,
	"Dan Nowlin" <dan.nowlin@intel.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Dongdong Liu" <liudongdong3@huawei.com>,
	"Ferruh Yigit" <ferruh.yigit@intel.com>,
	"Flavio Leitner" <fbl@sysclose.org>,
	"Grzegorz Siwik" <grzegorz.siwik@intel.com>,
	"Huisong Li" <lihuisong@huawei.com>,
	"Jingjing Wu" <jingjing.wu@intel.com>,
	"Kevin Liu" <kevinx.liu@intel.com>, "Ke Xu" <ke1.xu@intel.com>,
	"Konstantin Ananyev" <konstantin.ananyev@intel.com>,
	"Leyi Rong" <leyi.rong@intel.com>,
	"Lijun Ou" <oulijun@huawei.com>, "Matan Azrad" <matan@nvidia.com>,
	"Maxime Coquelin" <maxime.coquelin@redhat.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	"Paul M Stillwell Jr" <paul.m.stillwell.jr@intel.com>,
	"Qiming Yang" <qiming.yang@intel.com>,
	"Qi Zhang" <qi.z.zhang@intel.com>,
	"Ravi Kumar" <ravi1.kumar@amd.com>,
	"Roman Storozhenko" <roman.storozhenko@intel.com>,
	"Shahaf Shuler" <shahafs@nvidia.com>,
	"Shibin Koikkara Reeny" <shibin.koikkara.reeny@intel.com>,
	"Somnath Kotur" <somnath.kotur@broadcom.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Tiwei Bie" <tiwei.bie@intel.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	"Volodymyr Fialko" <vfialko@marvell.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"Wenzhuo Lu" <wenzhuo.lu@intel.com>,
	"Xuan Ding" <xuan.ding@intel.com>,
	"Yisen Zhuang" <yisen.zhuang@huawei.com>,
	"Yuan Wang" <yuanx.wang@intel.com>,
	"Zhichao Zeng" <zhichaox.zeng@intel.com>,
	"Zhimin Huang" <zhiminx.huang@intel.com>
Subject: Re: please help backporting some patches to stable release 20.11.7
Date: Fri, 4 Nov 2022 19:02:08 +0100	[thread overview]
Message-ID: <CAGtZVEsuqf+XJj_LQu4p=izgkpHOyms_NZc4xoMsMQhrCxj+UQ@mail.gmail.com> (raw)
In-Reply-To: <20221103094132.1103255-1-luca.boccassi@gmail.com>

Hi,

I don't think that 09b5b2880d ("net/bnxt: fix error code during MTU
change") is meant to be backported to 20.11 since it is a fix to
a42ab1eb33ff ("net/bnxt: disallow MTU change when device is started")
which seems to not have been backported, although I cannot find
confirmation that it should have been skipped for the 20.11.6 release.

Kind Regards,
Benjamin Le Berre.

On Thu, Nov 3, 2022 at 10:41 AM <luca.boccassi@gmail.com> wrote:
>
> 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 11/10/22.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.7
> 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
>
> ---
> 8ae946970e  Abdullah Ömer Yamaç eal: fix thread name for high order lcores
> 09b5b2880d  Benjamin Le Berre net/bnxt: fix error code during MTU change
> b38bd88beb  Huisong Li       net/hns3: fix clearing hardware MAC statistics
> 0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
> 8f81056e5a  Qi Zhang         net/ice/base: fix 100M speed capability
> 04ab2b2f0b  Qi Zhang         net/ice/base: fix comment of overloaded GCO bit
> 40ff47dd4b  Qi Zhang         net/ice/base: fix double VLAN in promiscuous mode
> b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
> 38ef9e1b99  Qi Zhang         net/ice/base: fix null pointer dereference
> 27b7bdae1d  Qi Zhang         net/ice: fix DDP package init
> 3b8c645afa  Zhichao Zeng     net/iavf: fix outer checksum flags
> 1aaacea174  Zhichao Zeng     net/iavf: fix processing VLAN TCI in SSE path

  parent reply	other threads:[~2022-11-04 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  9:40 luca.boccassi
     [not found] ` <20221103094132.1103255-1-luca.boccassi@gmail.com>
2022-11-04 18:02   ` Benjamin Le Berre [this message]
2022-11-08  2:00 ` lihuisong (C)
2022-11-08 10:25   ` Luca Boccassi
2022-11-09  2:23     ` lihuisong (C)
2022-11-05 17:26 luca.boccassi
2022-11-17 23:16 luca.boccassi

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='CAGtZVEsuqf+XJj_LQu4p=izgkpHOyms_NZc4xoMsMQhrCxj+UQ@mail.gmail.com' \
    --to=benjamin.le_berre@6wind.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akozyrev@nvidia.com \
    --cc=alice.michael@intel.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=anirudh.venkataramanan@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=damodharam.ammepalli@broadcom.com \
    --cc=dan.nowlin@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=fbl@sysclose.org \
    --cc=fengchunsong@huawei.com \
    --cc=ferruh.yigit@intel.com \
    --cc=gakhil@marvell.com \
    --cc=grzegorz.siwik@intel.com \
    --cc=humin29@huawei.com \
    --cc=jingjing.wu@intel.com \
    --cc=ke1.xu@intel.com \
    --cc=kevinx.liu@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=leyi.rong@intel.com \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=matan@nvidia.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=omer.yamac@ceng.metu.edu.tr \
    --cc=oulijun@huawei.com \
    --cc=paul.m.stillwell.jr@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=ravi1.kumar@amd.com \
    --cc=roman.storozhenko@intel.com \
    --cc=shahafs@nvidia.com \
    --cc=shibin.koikkara.reeny@intel.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=tiwei.bie@intel.com \
    --cc=vfialko@marvell.com \
    --cc=viacheslavo@nvidia.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xuan.ding@intel.com \
    --cc=yisen.zhuang@huawei.com \
    --cc=yuanx.wang@intel.com \
    --cc=zhichaox.zeng@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).