patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
To: dpdk stable <stable@dpdk.org>,
	"luca.boccassi@gmail.com" <luca.boccassi@gmail.com>
Subject: RE: please help backporting some patches to stable release 20.11.8
Date: Wed, 1 Mar 2023 16:15:11 +0000	[thread overview]
Message-ID: <MW4PR11MB5911D6F098161FEA6BC4BB5587AD9@MW4PR11MB5911.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230223094215.3927887-1-luca.boccassi@gmail.com>

Hi Luca,
     Below mentioned crypto patches has dependency on below commit

commit 2ae84b39ae7b92c6b72f9dc9aa0a4aa2572e10e1
Author: Ganapati Kundapura <ganapati.kundapura@intel.com>
Date:   Thu Feb 10 11:41:16 2022 -0600

    eventdev/crypto: store operations in circular buffer

    Move crypto ops to circular buffer to retain crypto
    ops when cryptodev/eventdev are temporarily full.

    Signed-off-by: Ganapati Kundapura <ganapati.kundapura@intel.com>
    Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>

Could you please pull this commit and try applying other patches?

Thanks,
Ganapati

> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Thursday, February 23, 2023 3:12 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; Akhil Goyal
> <akhil.goyal@nxp.com>; Alexander Kozyrev <akozyrev@nvidia.com>; Singh,
> Aman Deep <aman.deep.singh@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Bernard Iremonger
> <bernard.iremonger@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Chengchang Tang
> <tangchengchang@huawei.com>; Chengwen Feng
> <fengchengwen@huawei.com>; David Christensen
> <drc@linux.vnet.ibm.com>; Dongdong Liu <liudongdong3@huawei.com>;
> Ferruh Yigit <ferruh.yigit@amd.com>; Gage Eads <gage.eads@intel.com>;
> Kundapura, Ganapati <ganapati.kundapura@intel.com>; Hongbo Zheng
> <zhenghongbo3@huawei.com>; Huisong Li <lihuisong@huawei.com>; Jerin
> Jacob <jerinj@marvell.com>; Konstantin Ananyev
> <konstantin.ananyev@intel.com>; Lijun Ou <oulijun@huawei.com>; Matan
> Azrad <matan@nvidia.com>; Michael Qiu <michael.qiu@intel.com>; Min Hu
> (Connor) <humin29@huawei.com>; Neil Horman
> <nhorman@tuxdriver.com>; Nelio Laranjeiro <nelio.laranjeiro@6wind.com>;
> Rao, Nikhil <nikhil.rao@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Ray Kinsella <mdr@ashroe.eu>; Ruifeng
> Wang <ruifeng.wang@arm.com>; Shahaf Shuler <shahafs@nvidia.com>;
> Suanming Mou <suanmingm@nvidia.com>; Viacheslav Ovsiienko
> <viacheslavo@nvidia.com>; Wei Hu (Xavier) <xavier.huwei@huawei.com>;
> Lu, Wenzhuo <wenzhuo.lu@intel.com>; Yisen Zhuang
> <yisen.zhuang@huawei.com>; Yongseok Koh <yskoh@mellanox.com>
> Subject: please help backporting some patches to stable release 20.11.8
> 
> 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 02/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
> 
> ---
> 1f903ebe2c  Alexander Kozyrev net/mlx5: check compressed CQE opcode in
> vectorized Rx
> 27fd465215  Chengwen Feng    net/hns3: declare flow rule keeping capability
> cdede073a5  Ferruh Yigit     app/testpmd: fix link check condition on port start
> 04dac73643  Ganapati Kundapura eventdev/crypto: fix enqueue count
> 4b04134cbb  Ganapati Kundapura eventdev/crypto: fix failed events
> da73a2a0d1  Ganapati Kundapura eventdev/crypto: fix offset used while
> flushing events
> f442c04001  Ganapati Kundapura eventdev/crypto: fix overflow in circular
> buffer
> 52a4e960b4  Huisong Li       net/hns3: extract common function to query
> device
> 10f91af5a5  Huisong Li       net/hns3: fix burst mode query with dummy
> function
> 2aec7beaba  Huisong Li       net/hns3: make getting Tx function static
> a8d240786e  Huisong Li       net/hns3: remove debug condition for Tx prepare
> 6a934ba4c6  Huisong Li       net/hns3: separate Tx prepare from getting Tx
> function
> cedb44dc87  Suanming Mou     common/mlx5: improve AES-XTS tweak
> capability check
> 9b31fc9007  Viacheslav Ovsiienko net/mlx5: fix read device clock in real time
> mode

  reply	other threads:[~2023-03-01 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23  9:42 luca.boccassi
2023-03-01 16:15 ` Kundapura, Ganapati [this message]
2023-03-02  9:47   ` Luca Boccassi
2023-03-02 10:18     ` Kundapura, Ganapati
2023-03-21  9:29 ` lihuisong (C)
2023-03-15 22:49 luca.boccassi
2023-03-21  9:37 ` lihuisong (C)
2023-03-22  0:43 luca.boccassi
2023-03-29  1:05 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=MW4PR11MB5911D6F098161FEA6BC4BB5587AD9@MW4PR11MB5911.namprd11.prod.outlook.com \
    --to=ganapati.kundapura@intel.com \
    --cc=luca.boccassi@gmail.com \
    --cc=stable@dpdk.org \
    /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).