patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 23.11.2
@ 2024-07-12 11:08 Xueming Li
  2024-08-12 13:10 ` Xueming Li
  0 siblings, 1 reply; 3+ messages in thread
From: Xueming Li @ 2024-07-12 11:08 UTC (permalink / raw)
  Cc: dpdk stable, Harman Kalra, Kiran Kumar K, Nithin Dabilpuram,
	Satha Rao, Sunil Kumar Kori

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 23.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 23.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 07/19/24.

You can find the a temporary work-in-progress branch of the coming 23.11.2
release at:
    https://git.dpdk.org/dpdk-stable/log/?h=23.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=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 23.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 23.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 23.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Xueming Li <xuemingl@nvidia.com>

---
4c2f14bc6d  Sunil Kumar Kori net/cnxk: fix xstats reset

^ permalink raw reply	[flat|nested] 3+ messages in thread

* please help backporting some patches to stable release 23.11.2
  2024-07-12 11:08 please help backporting some patches to stable release 23.11.2 Xueming Li
@ 2024-08-12 13:10 ` Xueming Li
  2024-08-14  2:40   ` Chaoyong He
  0 siblings, 1 reply; 3+ messages in thread
From: Xueming Li @ 2024-08-12 13:10 UTC (permalink / raw)
  Cc: dpdk stable, Niklas Söderlund, Bruce Richardson,
	Chaoyong He, Ciara Loftus, Ferruh Yigit, Frank Du, Harman Kalra,
	Ian Stokes, Jack Bond-Preston, Jacob Keller, Junfeng Guo, Kai Ji,
	Kevin Laatz, Kiran Kumar K, Long Wu, Maryam Tahhan,
	Morten Brørup, Nithin Dabilpuram, Peng Zhang, Qi Zhang,
	Rahul Bhansali, Ray Kinsella, Satha Rao, Satheesh Paul,
	Sunil Kumar Kori, Tomasz Wakula, Wathsala Vithanage, Xiaolong Ye

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 23.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 23.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 08/19/24.

You can find the a temporary work-in-progress branch of the coming 23.11.2
release at:
    https://git.dpdk.org/dpdk-stable/log/?h=23.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=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 23.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 23.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 23.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Xueming Li <xuemingl@nvidia.com>

---
3a64e190bc  Chaoyong He      net/nfp: fix firmware abnormal cleanup
78bbab1628  Chaoyong He      net/nfp: forbid offload flow rules with empty action list
97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
17d5bc6135  Jack Bond-Preston crypto/openssl: make per-QP auth context clones
ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor port
fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM
df44ba7a3c  Tomasz Wakula    net/ice/base: fix preparing PHY for timesync command

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: please help backporting some patches to stable release 23.11.2
  2024-08-12 13:10 ` Xueming Li
@ 2024-08-14  2:40   ` Chaoyong He
  0 siblings, 0 replies; 3+ messages in thread
From: Chaoyong He @ 2024-08-14  2:40 UTC (permalink / raw)
  To: Xueming Li; +Cc: dpdk stable

Hi Xueming,

ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor port

This patch needs not be backported.

Thanks.

> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Monday, August 12, 2024 9:10 PM
> Cc: dpdk stable <stable@dpdk.org>; Niklas Söderlund
> <niklas.soderlund@corigine.com>; Bruce Richardson
> <bruce.richardson@intel.com>; Chaoyong He <chaoyong.he@corigine.com>;
> Ciara Loftus <ciara.loftus@intel.com>; Ferruh Yigit <ferruh.yigit@amd.com>;
> Frank Du <frank.du@intel.com>; Harman Kalra <hkalra@marvell.com>; Ian
> Stokes <ian.stokes@intel.com>; Jack Bond-Preston <jack.bond-
> preston@foss.arm.com>; Jacob Keller <jacob.e.keller@intel.com>; Junfeng
> Guo <junfeng.guo@intel.com>; Kai Ji <kai.ji@intel.com>; Kevin Laatz
> <kevin.laatz@intel.com>; Kiran Kumar K <kirankumark@marvell.com>; Long
> Wu <Long.Wu@nephogine.com>; Maryam Tahhan <mtahhan@redhat.com>;
> Morten Brørup <mb@smartsharesystems.com>; Nithin Dabilpuram
> <ndabilpuram@marvell.com>; Nole Zhang <peng.zhang@corigine.com>; Qi
> Zhang <qi.z.zhang@intel.com>; Rahul Bhansali <rbhansali@marvell.com>; Ray
> Kinsella <mdr@ashroe.eu>; Satha Rao <skoteshwar@marvell.com>; Satheesh
> Paul <psatheesh@marvell.com>; Sunil Kumar Kori <skori@marvell.com>;
> Tomasz Wakula <tomaszx.wakula@intel.com>; Wathsala Vithanage
> <wathsala.vithanage@arm.com>; Xiaolong Ye <xiaolong.ye@intel.com>
> Subject: please help backporting some patches to stable release 23.11.2
> 
> 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 23.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 23.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 08/19/24.
> 
> You can find the a temporary work-in-progress branch of the coming 23.11.2
> release at:
>     https://git.dpdk.org/dpdk-stable/log/?h=23.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=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
> 
> When sending the backported patch, please indicate the target branch in the
> subject line, as we have multiple branches, for example:
>     [PATCH 23.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 23.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 23.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Xueming Li <xuemingl@nvidia.com>
> 
> ---
> 3a64e190bc  Chaoyong He      net/nfp: fix firmware abnormal cleanup
> 78bbab1628  Chaoyong He      net/nfp: forbid offload flow rules with empty
> action list
> 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
> 17d5bc6135  Jack Bond-Preston crypto/openssl: make per-QP auth context
> clones
> ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF
> representor port
> fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM
> df44ba7a3c  Tomasz Wakula    net/ice/base: fix preparing PHY for timesync
> command

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-08-14  2:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-07-12 11:08 please help backporting some patches to stable release 23.11.2 Xueming Li
2024-08-12 13:10 ` Xueming Li
2024-08-14  2:40   ` Chaoyong He

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).