From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: dpdk stable <stable@dpdk.org>, Kevin Traynor <ktraynor@redhat.com>
Cc: "Vargas, Hernan" <hernan.vargas@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: RE: please help backporting some patches to stable release 21.11.4
Date: Sat, 4 Mar 2023 00:28:01 +0000 [thread overview]
Message-ID: <BY5PR11MB44518C53D93B2F2EFC0087D6F8B09@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230228182517.205774-1-ktraynor@redhat.com>
Hi Kevin,
This one in the PMD is not required
e77d682aad Nicolas Chautru baseband/acc100: fix input error related to padding
as 2 fixes were already combined into one by Hernan in commit 9e244f70bcf8cccd1faa60b07cf659251d293097 on the 21.11 stable branch
This one is arguably not required as this is test application variant is not built by default on the 21.11 branch.
8abe31b1d9 Nicolas Chautru app/bbdev: add allocation checks
Thanks
Nic
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Tuesday, February 28, 2023 10:25 AM
> To: dpdk stable <stable@dpdk.org>
> Cc: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; Akhil Goyal
> <gakhil@marvell.com>; Anoob Joseph <anoobj@marvell.com>; Xia, Chenbo
> <chenbo.xia@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; David Marchand
> <david.marchand@redhat.com>; Dongdong Liu <liudongdong3@huawei.com>;
> Fan Zhang <fanzhang.oss@gmail.com>; Fengnan Chang
> <changfengnan@bytedance.com>; Kundapura, Ganapati
> <ganapati.kundapura@intel.com>; Hanumanth Pothula
> <hpothula@marvell.com>; Harman Kalra <hkalra@marvell.com>; Huisong Li
> <lihuisong@huawei.com>; Jiawen Wu <jiawenwu@trustnetic.com>; Ji, Kai
> <kai.ji@intel.com>; Kiran Kumar K <kirankumark@marvell.com>; Matan Azrad
> <matan@nvidia.com>; Maxime Coquelin <maxime.coquelin@redhat.com>;
> Chautru, Nicolas <nicolas.chautru@intel.com>; Nithin Dabilpuram
> <ndabilpuram@marvell.com>; Pavan Nikhilesh <pbhagavatula@marvell.com>;
> Zhang, Qi Z <qi.z.zhang@intel.com>; Satheesh Paul
> <psatheesh@marvell.com>; Shijith Thotton <sthotton@marvell.com>; Stephen
> Hemminger <stephen@networkplumber.org>; Steve Yang
> <stevex.yang@intel.com>; Suanming Mou <suanmingm@nvidia.com>; Tyler
> Retzlaff <roretzla@linux.microsoft.com>; Viacheslav Ovsiienko
> <viacheslavo@nvidia.com>; Jangra, Yogesh <yogesh.jangra@intel.com>
> Subject: please help backporting some patches to stable release 21.11.4
>
> 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 21.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 21.11 branch, or
> - Indicate that the patch should not be backported
>
> Please do either of the above by 03/06/23.
>
> You can find the a temporary work-in-progress branch of the coming 21.11.4
> release at:
> https://github.com/kevintraynor/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 21.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
> --subject-prefix='PATCH 21.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 21.11 is located at tree:
> https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Kevin
>
> ---
> c5b531d6ee Anoob Joseph app/crypto-perf: fix session freeing
> cc75968228 Fengnan Chang eal: cleanup alarm and hotplug before memory
> detach
> 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 5a0f64d84b Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx
> queues
> 59ceaa72d5 Harman Kalra common/cnxk: fix part number for CN10K
> 4ba28c957a Huisong Li net/hns3: extract common functions to set Rx/Tx
> 10f91af5a5 Huisong Li net/hns3: fix burst mode query with dummy function
> 5172f9c464 Huisong Li net/hns3: fix RSS key size compatibility
> 2aec7beaba Huisong Li net/hns3: make getting Tx function static
> 6a934ba4c6 Huisong Li net/hns3: separate Tx prepare from getting Tx
> function
> 31a28a99fd Jiawen Wu net/ngbe: add spinlock protection on YT PHY
> 585283f9a7 Maxime Coquelin vhost: fix possible FD leaks
> 8abe31b1d9 Nicolas Chautru app/bbdev: add allocation checks e77d682aad
> Nicolas Chautru baseband/acc100: fix input error related to padding
> 5781638519 Nithin Dabilpuram common/cnxk: fix RQ mask config for CN10KB
> chip 3fe71706ab Pavan Nikhilesh event/cnxk: fix stale data in workslot
> 927cb43fe9 Pavan Nikhilesh examples/l3fwd: fix port group mask with AltiVec
> 4741248656 Satheesh Paul common/cnxk: fix dual VLAN parsing
> 2245ccf746 Stephen Hemminger crypto/ipsec_mb: remove unnecessary null
> check
> 0f044b6681 Steve Yang net/iavf: fix refine protocol header
> 0b241667cc Steve Yang net/iavf: fix tainted scalar
> b125c0e721 Steve Yang net/iavf: fix tainted scalar
> cedb44dc87 Suanming Mou common/mlx5: improve AES-XTS tweak capability
> check
> 9b31fc9007 Viacheslav Ovsiienko net/mlx5: fix read device clock in real time
> mode
> a774cba0bb Yogesh Jangra pipeline: fix validate header instruction
next prev parent reply other threads:[~2023-03-04 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 18:25 Kevin Traynor
2023-03-01 16:16 ` Kundapura, Ganapati
2023-03-03 11:45 ` Kevin Traynor
2023-03-04 0:28 ` Chautru, Nicolas [this message]
2023-03-15 14:26 ` Kevin Traynor
2023-03-15 14:38 Kevin Traynor
2023-03-20 3:30 ` Su, Simei
2023-03-20 15:23 ` Kevin Traynor
2023-03-22 11:01 Kevin Traynor
2023-03-22 15:54 ` Niklas Söderlund
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=BY5PR11MB44518C53D93B2F2EFC0087D6F8B09@BY5PR11MB4451.namprd11.prod.outlook.com \
--to=nicolas.chautru@intel.com \
--cc=hernan.vargas@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.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).