patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: dpdk stable <stable@dpdk.org>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Chengchang Tang <tangchengchang@huawei.com>,
	 Chengwen Feng <fengchengwen@huawei.com>,
	Gregory Etelson <getelson@mellanox.com>,
	 Jeff Guo <jia.guo@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Matan Azrad <matan@mellanox.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Michael Baum <michaelba@mellanox.com>,
	Min Hu <humin29@huawei.com>,
	 Narcisa Vasile <navasile@linux.microsoft.com>,
	Olivier Matz <olivier.matz@6wind.com>,
	 Ophir Munk <ophirmu@mellanox.com>, Ori Kam <orika@mellanox.com>,
	 Pallavi Kadam <pallavi.kadam@intel.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	 Qi Zhang <qi.z.zhang@intel.com>,
	Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
	 Ranjit Menon <ranjit.menon@intel.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Ray Kinsella <mdr@ashroe.eu>,
	Sarosh Arif <sarosh.arif@emumba.com>,
	 Shougang Wang <shougangx.wang@intel.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	 Suanming Mou <suanmingm@mellanox.com>,
	Tasnim Bashar <tbashar@mellanox.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	Wei Hu <xavier.huwei@huawei.com>,  Wei Zhao <wei.zhao1@intel.com>,
	Xueming Li <xuemingl@mellanox.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.4
Date: Wed, 12 Aug 2020 09:14:57 +0530	[thread overview]
Message-ID: <CAH-L+nOmOY_Go1FgvzhVmUf6Og=VCToc2dtAi9YkhNAkcU1orw@mail.gmail.com> (raw)
In-Reply-To: <20200810111818.61635-1-luca.boccassi@gmail.com>

Hi Luca,

On Mon, Aug 10, 2020 at 4:48 PM <luca.boccassi@gmail.com> wrote:

> Hi commit authors (and maintainers),
>
> I didn't apply following commits from DPDK master to 19.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 19.11 branch, or
>     - Indicate that the patch should not be backported
>
> Please do either of the above by August the 17th.
> If you'd like to backport the patches but cannot make it by the above
> deadline,
> please let us know and we'll discuss whether the release can be postponed.
>
>
> Some notes on stable backports:
>
> A backport should contain a reference to the DPDK master branch commit
> in it's commit message in the following fashion:
>     [ upstream commit <commit's dpdk master 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 19.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 19.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 19.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 750ff30a8  Gregory Etelson  net/mlx5: fix tunnel flow priority
> 71fa6a996  Jeff Guo         net/ice: fix hash action validation
> 0466d286c  Kalesh AP        net/bnxt: fix setting link speed
>
[Kalesh]: This is dependent on another patch which has not been back ported
to 19.11 branch. I have pushed both the patches for 19.11 now.

d4d5a0411  Kalesh AP        net/bnxt: fix unnecessary memory allocation
>
[Kalesh]: It looks the commit it was trying to fix is not back ported to
19.11 branch. So you can ignore this commit for now.

Regards,
Kalesh


> 473d8e67d  Matan Azrad      common/mlx5: add virtio queue protection domain
> 04e7beeb1  Matan Azrad      vdpa/mlx5: adjust virtio queue protection
> domain
> ebed623f6  Michael Baum     net/mlx5: fix hairpin Rx queue creation error
> path
> 7e6eba619  Michael Baum     net/mlx5: fix hairpin Tx queue creation error
> path
> cb4261e0b  Pavan Nikhilesh  event/octeontx2: improve datapath memory
> locality
> e0e1496be  Rahul Lakkireddy net/cxgbe: fix L2T leak in filter error and
> free path
> 01186263c  Shougang Wang    net/ice: fix EEPROM data
> e1293b10d  Suanming Mou     net/mlx5: fix counter query
> fc9b57ff5  Wei Hu (Xavier)  net/hns3: fix inserted VLAN tag position in Tx
> 6c44219f9  Wei Hu (Xavier)  net/hns3: fix reassembling multiple segment
> packets in Tx
> 2d6255ff0  Wei Zhao         net/ice/base: fix tunnel filtering rule
> ea1e91e96  Wei Zhao         net/ice: fix tunnel type for switch rule
> 86035f97f  Wei Zhao         net/ice: support switch flow for specific L4
> type
>


-- 
Regards,
Kalesh A P

  parent reply	other threads:[~2020-08-12  3:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200810111818.61635-1-luca.boccassi@gmail.com>
2020-08-11  8:18 ` Matan Azrad
2020-08-11 17:57   ` Luca Boccassi
2020-08-12  3:44 ` Kalesh Anakkur Purayil [this message]
2020-08-13  6:10 ` Wang, ShougangX
2020-08-10 11:18 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='CAH-L+nOmOY_Go1FgvzhVmUf6Og=VCToc2dtAi9YkhNAkcU1orw@mail.gmail.com' \
    --to=kalesh-anakkur.purayil@broadcom.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=fengchengwen@huawei.com \
    --cc=getelson@mellanox.com \
    --cc=humin29@huawei.com \
    --cc=jia.guo@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=matan@mellanox.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdr@ashroe.eu \
    --cc=michaelba@mellanox.com \
    --cc=navasile@linux.microsoft.com \
    --cc=olivier.matz@6wind.com \
    --cc=ophirmu@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=pallavi.kadam@intel.com \
    --cc=pbhagavatula@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rahul.lakkireddy@chelsio.com \
    --cc=ranjit.menon@intel.com \
    --cc=rasland@mellanox.com \
    --cc=sarosh.arif@emumba.com \
    --cc=shougangx.wang@intel.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@mellanox.com \
    --cc=tangchengchang@huawei.com \
    --cc=tbashar@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=wei.zhao1@intel.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xuemingl@mellanox.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).