patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 22.11.6
@ 2024-06-25  0:04 luca.boccassi
  0 siblings, 0 replies; 4+ messages in thread
From: luca.boccassi @ 2024-06-25  0:04 UTC (permalink / raw)
  To: dpdk stable
  Cc: Aman Singh, Andrew Rybchenko, Beilei Xing, Bing Zhao,
	Chengwen Feng, Cristian Dumitrescu, Dariusz Sosnowski,
	Dengdui Huang, Dmitry Kozlyuk, Ferruh Yigit, Hongbo Li,
	Jerin Jacob, Jingjing Wu, Kaiwen Deng, Kiran Kumar K,
	Lunyuan Cui, Matan Azrad, Morten Brørup, Nithin Dabilpuram,
	Qi Zhang, Rahul Lakkireddy, Ray Kinsella, Satha Rao,
	Sunil Kumar Kori, Thomas Monjalon, Xiaolong Ye, Yuying Zhang,
	Zhichao Zeng

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 2024/07/01.

You can find the a temporary work-in-progress branch of the coming 22.11.6
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 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.

Luca Boccassi

---
ecf408d2aa  Bing Zhao        app/testpmd: fix indirect action flush
b9a87346b0  Chengwen Feng    ethdev: fix strict aliasing in link up
0f9ec0cbd2  Kaiwen Deng      net/iavf: fix VF reset when using DCF
590ee5cd95  Nithin Dabilpuram net/cnxk: update SA userdata and keep original cookie
4c2f14bc6d  Sunil Kumar Kori net/cnxk: fix xstats reset

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

* RE: please help backporting some patches to stable release 22.11.6
  2024-07-16 10:30   ` Luca Boccassi
@ 2024-07-17  1:57     ` Du, Frank
  0 siblings, 0 replies; 4+ messages in thread
From: Du, Frank @ 2024-07-17  1:57 UTC (permalink / raw)
  To: Luca Boccassi; +Cc: dpdk stable

Hi,

Ok, so please not backport this XDP commit. It's fine as most XDP PMD user is likely to use the latest version.

Thanks,
Frank

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Tuesday, July 16, 2024 6:30 PM
> To: Du, Frank <frank.du@intel.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: Re: please help backporting some patches to stable release 22.11.6
> 
> Hi,
> 
> That mempool patch introduces a new API, so it is not appropriate for
> backporting. If you need this bug fix in 22.11.6, then a 22.11.x specific patch is
> needed for it, that doesn't change the library API.
> 
> On Tue, 16 Jul 2024 at 03:44, Du, Frank <frank.du@intel.com> wrote:
> >
> > Hi Luca,
> >
> > For this one:
> > 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
> >
> > It depends on another mempool patch:
> >
> https://github.com/DPDK/dpdk/commit/2f1015d8d56d32465cc260faf469950
> ebb
> > 9cf73b
> >
> > I guess it can pass the build if the dependency patch is cherry-picked also.
> >
> > Thanks,
> > Frank
> >
> > > -----Original Message-----
> > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > > Sent: Monday, July 15, 2024 11:33 PM
> > > To: dpdk stable <stable@dpdk.org>
> > > Cc: Richardson, Bruce <bruce.richardson@intel.com>; Chaoyong He
> > > <chaoyong.he@corigine.com>; Loftus, Ciara <ciara.loftus@intel.com>;
> > > Ferruh Yigit <ferruh.yigit@amd.com>; Du, Frank <frank.du@intel.com>;
> > > Stokes, Ian <ian.stokes@intel.com>; Keller, Jacob E
> > > <jacob.e.keller@intel.com>; Laatz, Kevin <kevin.laatz@intel.com>;
> > > Kiran Kumar K <kirankumark@marvell.com>; Long Wu
> > > <long.wu@corigine.com>; Morten Brørup <mb@smartsharesystems.com>;
> > > Niklas Söderlund <niklas.soderlund@corigine.com>; Nithin Dabilpuram
> > > <ndabilpuram@marvell.com>; Stillwell Jr, Paul M
> > > <paul.m.stillwell.jr@intel.com>; Peng Zhang
> > > <peng.zhang@corigine.com>; Yang, Qiming <qiming.yang@intel.com>;
> > > Zhang, Qi Z <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>; Xiaolong Ye
> > > <xiaolong.ye@intel.com>
> > > Subject: please help backporting some patches to stable release
> > > 22.11.6
> > >
> > > 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 07/22/24.
> > >
> > > You can find the a temporary work-in-progress branch of the coming
> > > 22.11.6 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 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.
> > >
> > > Luca Boccassi
> > >
> > > ---
> > > 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from
> mempool
> > > ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF
> representor
> > > port
> > > fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and
> MCAM

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

* Re: please help backporting some patches to stable release 22.11.6
       [not found] ` <PH0PR11MB477576B152FD2BAAD2D9B97580A22@PH0PR11MB4775.namprd11.prod.outlook.com>
@ 2024-07-16 10:30   ` Luca Boccassi
  2024-07-17  1:57     ` Du, Frank
  0 siblings, 1 reply; 4+ messages in thread
From: Luca Boccassi @ 2024-07-16 10:30 UTC (permalink / raw)
  To: Du, Frank; +Cc: dpdk stable

Hi,

That mempool patch introduces a new API, so it is not appropriate for
backporting. If you need this bug fix in 22.11.6, then a 22.11.x
specific patch is needed for it, that doesn't change the library API.

On Tue, 16 Jul 2024 at 03:44, Du, Frank <frank.du@intel.com> wrote:
>
> Hi Luca,
>
> For this one:
> 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
>
> It depends on another mempool patch: https://github.com/DPDK/dpdk/commit/2f1015d8d56d32465cc260faf469950ebb9cf73b
>
> I guess it can pass the build if the dependency patch is cherry-picked also.
>
> Thanks,
> Frank
>
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Monday, July 15, 2024 11:33 PM
> > To: dpdk stable <stable@dpdk.org>
> > Cc: Richardson, Bruce <bruce.richardson@intel.com>; Chaoyong He
> > <chaoyong.he@corigine.com>; Loftus, Ciara <ciara.loftus@intel.com>; Ferruh
> > Yigit <ferruh.yigit@amd.com>; Du, Frank <frank.du@intel.com>; Stokes, Ian
> > <ian.stokes@intel.com>; Keller, Jacob E <jacob.e.keller@intel.com>; Laatz, Kevin
> > <kevin.laatz@intel.com>; Kiran Kumar K <kirankumark@marvell.com>; Long Wu
> > <long.wu@corigine.com>; Morten Brørup <mb@smartsharesystems.com>;
> > Niklas Söderlund <niklas.soderlund@corigine.com>; Nithin Dabilpuram
> > <ndabilpuram@marvell.com>; Stillwell Jr, Paul M
> > <paul.m.stillwell.jr@intel.com>; Peng Zhang <peng.zhang@corigine.com>; Yang,
> > Qiming <qiming.yang@intel.com>; Zhang, Qi Z <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>; Xiaolong Ye <xiaolong.ye@intel.com>
> > Subject: please help backporting some patches to stable release 22.11.6
> >
> > 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 07/22/24.
> >
> > You can find the a temporary work-in-progress branch of the coming 22.11.6
> > 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 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.
> >
> > Luca Boccassi
> >
> > ---
> > 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
> > ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor
> > port
> > fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM

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

* please help backporting some patches to stable release 22.11.6
@ 2024-07-15 15:32 luca.boccassi
       [not found] ` <PH0PR11MB477576B152FD2BAAD2D9B97580A22@PH0PR11MB4775.namprd11.prod.outlook.com>
  0 siblings, 1 reply; 4+ messages in thread
From: luca.boccassi @ 2024-07-15 15:32 UTC (permalink / raw)
  To: dpdk stable
  Cc: Bruce Richardson, Chaoyong He, Ciara Loftus, Ferruh Yigit,
	Frank Du, Ian Stokes, Jacob Keller, Kevin Laatz, Kiran Kumar K,
	Long Wu, Morten Brørup, Niklas Söderlund,
	Nithin Dabilpuram, Paul M Stillwell Jr, Peng Zhang, Qiming Yang,
	Qi Zhang, Rahul Bhansali, Ray Kinsella, Satha Rao, Satheesh Paul,
	Sunil Kumar Kori, 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 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 07/22/24.

You can find the a temporary work-in-progress branch of the coming 22.11.6
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 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.

Luca Boccassi

---
97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor port
fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM

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

end of thread, other threads:[~2024-07-17  1:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-25  0:04 please help backporting some patches to stable release 22.11.6 luca.boccassi
2024-07-15 15:32 luca.boccassi
     [not found] ` <PH0PR11MB477576B152FD2BAAD2D9B97580A22@PH0PR11MB4775.namprd11.prod.outlook.com>
2024-07-16 10:30   ` Luca Boccassi
2024-07-17  1:57     ` Du, Frank

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