From: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
To: dpdk stable <stable@dpdk.org>
Cc: Luca Boccassi <bluca@debian.org>,
Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Dan Nowlin <dan.nowlin@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Leyi Rong <leyi.rong@intel.com>,
Michael Baucom <michael.baucom@broadcom.com>,
Mingjin Ye <mingjinx.ye@intel.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Randy Schacher <stuart.schacher@broadcom.com>,
Satha Rao <skoteshwar@marvell.com>,
Shahaji Bhosle <sbhosle@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Sunil Kumar Kori <skori@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: RE: please help backporting some patches to stable release 22.11.3
Date: Fri, 11 Aug 2023 10:24:50 -0400 [thread overview]
Message-ID: <c586d0de1a74e2d5c9774416a9d94cdb@mail.gmail.com> (raw)
In-Reply-To: <20230810000641.1953-1-xuemingl@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]
Hi Xueming,
The patch "8c047e823a Kishore Padmanabha net/bnxt: fix multi-root card
support" is not required for 22.11 release. This need not be backported to
older branch.
Thanks,
Kishore
-----Original Message-----
From: Xueming Li <xuemingl@nvidia.com>
Sent: Wednesday, August 9, 2023 8:07 PM
Cc: dpdk stable <stable@dpdk.org>; Luca Boccassi <bluca@debian.org>; Ajit
Khaparde <ajit.khaparde@broadcom.com>; Ankur Dwivedi
<adwivedi@marvell.com>; Anoob Joseph <anoobj@marvell.com>; Dan Nowlin
<dan.nowlin@intel.com>; Gowrishankar Muthukrishnan
<gmuthukrishn@marvell.com>; Harman Kalra <hkalra@marvell.com>; Jerin Jacob
<jerinj@marvell.com>; Kiran Kumar K <kirankumark@marvell.com>; Kishore
Padmanabha <kishore.padmanabha@broadcom.com>; Leyi Rong
<leyi.rong@intel.com>; Mike Baucom <michael.baucom@broadcom.com>; Mingjin
Ye <mingjinx.ye@intel.com>; Nithin Dabilpuram <ndabilpuram@marvell.com>;
Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>; Qiming Yang
<qiming.yang@intel.com>; Qi Zhang <qi.z.zhang@intel.com>; Randy Schacher
<stuart.schacher@broadcom.com>; Satha Rao <skoteshwar@marvell.com>;
Shahaji Bhosle <sbhosle@broadcom.com>; Somnath Kotur
<somnath.kotur@broadcom.com>; Sunil Kumar Kori <skori@marvell.com>;
Tejasree Kondoj <ktejasree@marvell.com>; Venkat Duvvuru
<venkatkumar.duvvuru@broadcom.com>
Subject: please help backporting some patches to stable release 22.11.3
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 22.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 22.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 08/16/23.
You can find the a temporary work-in-progress branch of the coming 22.11.3
release at:
https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
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=d90e6ae6f936ecdc2fd381
1ff9f26aec7f3c06eb
When sending the backported patch, please indicate the target branch in
the subject line, as we have multiple branches, for example:
[PATCH 22.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 22.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 22.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Xueming Li <xuemingl@nvidia.com>
---
3885644d91 Gowrishankar Muthukrishnan crypto/cnxk: fix order of ECFPM
parameters
1c7a4d37e7 Harman Kalra common/cnxk: fix mailbox timeout due to
deadlock
8c047e823a Kishore Padmanabha net/bnxt: fix multi-root card support
6fd3a7a618 Mingjin Ye net/ice/base: fix internal etype in switch
filter
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4227 bytes --]
next prev parent reply other threads:[~2023-08-11 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:06 Xueming Li
2023-08-11 14:24 ` Kishore Padmanabha [this message]
2023-08-15 13:02 ` Xueming(Steven) Li
[not found] <20230619022416.13730-1-xuemingl@nvidia.com>
2023-06-20 1:40 ` huangdengdui
2023-06-20 5:50 ` Xueming(Steven) Li
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=c586d0de1a74e2d5c9774416a9d94cdb@mail.gmail.com \
--to=kishore.padmanabha@broadcom.com \
--cc=adwivedi@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anoobj@marvell.com \
--cc=bluca@debian.org \
--cc=dan.nowlin@intel.com \
--cc=gmuthukrishn@marvell.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ktejasree@marvell.com \
--cc=leyi.rong@intel.com \
--cc=michael.baucom@broadcom.com \
--cc=mingjinx.ye@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=paul.m.stillwell.jr@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=sbhosle@broadcom.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=stuart.schacher@broadcom.com \
--cc=venkatkumar.duvvuru@broadcom.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).