patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 21.11.2
@ 2022-06-24 16:31 Kevin Traynor
  2022-06-27  9:15 ` Stanisław Kardach
                   ` (6 more replies)
  0 siblings, 7 replies; 22+ messages in thread
From: Kevin Traynor @ 2022-06-24 16:31 UTC (permalink / raw)
  To: dpdk stable
  Cc: Andrew Rybchenko, Anoob Joseph, Arek Kusztal, Bruce Richardson,
	Chaoyong He, Chengwen Feng, Conor Walsh, Dariusz Sosnowski,
	David Marchand, Daxue Gao, Fan Zhang, Harman Kalra,
	Jasvinder Singh, Jerin Jacob, Li Zhang, Louis Peens, Matan Azrad,
	Maxime Coquelin, Morten Brørup, Niklas Söderlund,
	Nithin Dabilpuram, Pavan Nikhilesh, Peng Zhang, Rahul Lakkireddy,
	Stanislaw Kardach, Stephen Hemminger, Sunil Kumar Kori,
	Timothy McDaniel, Viacheslav Ovsiienko, Walter Heymans, Yajun Wu,
	Luca Boccassi

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

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

---
These commits have non-trivial conflicts while applying to 21.11 branch:
4c1a91b21f  Arek Kusztal     crypto/qat: fix cleanup function default behaviour
5b4d317d83  Arek Kusztal     crypto/qat: fix missing copy guards in asym mod
d2fa2632a4  Dariusz Sosnowski net/mlx5: fix RSS hash types adjustment
a31c9f970d  David Marchand   net/cnxk: fix crash in IPsec telemetry
6cef22dcfe  Harman Kalra     net/cnxk: fix PFC class disabling
6f065d1539  Li Zhang         vdpa/mlx5: fix maximum number of virtqs
b2c5ff1bd9  Nithin Dabilpuram common/cnxk: fix mbox structs to avoid unaligned access
14124e48a3  Nithin Dabilpuram net/cnxk: fix hotplug detach for first device
e2819fea94  Nithin Dabilpuram net/cnxk: fix multi-segment extraction in vwqe path
2e668c547f  Nithin Dabilpuram net/cnxk: fix roundup size with transport mode
417be15e5f  Peng Zhang       net/nfp: make sure MTU is never larger than mbuf size
694c75e8e3  Rahul Lakkireddy test/crypto: fix build with optimization=1
c65e343c14  Stanislaw Kardach ci: enable C++ check for Arm and PPC
f75dd6d3b1  Stanislaw Kardach config: fix C++ cross compiler for Arm and PPC
174f2f3512  Sunil Kumar Kori common/cnxk: add PFC support for VF
95af59b7ad  Yajun Wu         vdpa/mlx5: workaround VAR offset within page

These commits apply cleanly to 21.11 branch but cause build errors:
aa802b1023  Bruce Richardson dma/idxd: fix AVX2 in non-datapath functions
(^ commit causes build error on OBS CentOS7. No need to rework, can take
when fix arives on DPDK main)

14124e48a3  Nithin Dabilpuram net/cnxk: fix hotplug detach for first device
485df8847a  Chengwen Feng    ethdev: clarify null location case in xstats get
45a192b2b4  Stephen Hemminger sched: fix floating point math
87ecdd9e7f  Timothy McDaniel event/dlb2: improve enqueue efficiency


^ permalink raw reply	[flat|nested] 22+ messages in thread
* please help backporting some patches to stable release 21.11.2
@ 2022-06-21 10:02 Kevin Traynor
  2022-06-22  2:57 ` Jiawen Wu
                   ` (4 more replies)
  0 siblings, 5 replies; 22+ messages in thread
From: Kevin Traynor @ 2022-06-21 10:02 UTC (permalink / raw)
  To: dpdk stable
  Cc: Ajit Khaparde, Andrew Rybchenko, Chaoyong He, Chengwen Feng,
	Dariusz Sosnowski, Gagandeep Singh, Jerin Jacob, Jiawen Wu,
	Kalesh AP, Louis Peens, Morten Brørup,
	Niklas Söderlund, Nithin Dabilpuram, Pavan Nikhilesh,
	Peng Zhang, Qi Zhang, Somnath Kotur, Viacheslav Ovsiienko,
	Walter Heymans, Yiding Zhou

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 06/23/22.

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

---
These commits have non-trivial conflicts while applying to 21.11 branch:
d2fa2632a4  Dariusz Sosnowski net/mlx5: fix RSS hash types adjustment
13ce268103  Gagandeep Singh  common/dpaax: remove dead code
708ebe7d03  Jiawen Wu        net/ngbe: fix external PHY power down
6dcfb19f60  Jiawen Wu        net/ngbe: fix reading M88E1512 PHY mode
696a821178  Jiawen Wu        net/ngbe: redesign internal PHY init flow
e2819fea94  Nithin Dabilpuram net/cnxk: fix multi-segment extraction in vwqe path
2e668c547f  Nithin Dabilpuram net/cnxk: fix roundup size with transport mode
417be15e5f  Peng Zhang       net/nfp: make sure MTU is never larger than mbuf size

These commits apply cleanly to 21.11 branch but cause build errors:
14124e48a3  Nithin Dabilpuram net/cnxk: fix hotplug detach for first device
c0278f6e52  Kalesh AP        net/bnxt: fix tunnel stateless offloads
485df8847a  Chengwen Feng    ethdev: clarify null location case in xstats get
676d986b4b  Yiding Zhou      net/iavf: fix crash after VF reset failure


^ permalink raw reply	[flat|nested] 22+ messages in thread
* please help backporting some patches to stable release 21.11.2
@ 2022-05-10 13:00 Kevin Traynor
  0 siblings, 0 replies; 22+ messages in thread
From: Kevin Traynor @ 2022-05-10 13:00 UTC (permalink / raw)
  To: dpdk stable
  Cc: Dariusz Sosnowski, Gagandeep Singh, Matan Azrad, Michael Baum,
	Viacheslav Ovsiienko

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 05/17/22.

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

---
d2fa2632a4  Dariusz Sosnowski net/mlx5: fix RSS hash types adjustment
13ce268103  Gagandeep Singh  common/dpaax: remove dead code
7a99336865  Michael Baum     net/mlx5: fix LRO configuration in drop Rx queue
a213b86821  Michael Baum     net/mlx5: fix LRO validation in Rx setup


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

end of thread, other threads:[~2022-08-01 13:31 UTC | newest]

Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-24 16:31 please help backporting some patches to stable release 21.11.2 Kevin Traynor
2022-06-27  9:15 ` Stanisław Kardach
2022-06-28 14:14   ` Kevin Traynor
2022-06-27 13:39 ` Rahul Lakkireddy
2022-06-28 14:18   ` Kevin Traynor
2022-06-27 21:15 ` McDaniel, Timothy
2022-06-28 14:13   ` Kevin Traynor
2022-06-28 14:20 ` Kevin Traynor
2022-06-29 10:24 ` Niklas Söderlund
2022-07-01 16:06   ` Kevin Traynor
2022-07-06 20:40 ` luca.boccassi
2022-08-01 13:31 ` McDaniel, Timothy
  -- strict thread matches above, loose matches on Subject: below --
2022-06-21 10:02 Kevin Traynor
2022-06-22  2:57 ` Jiawen Wu
2022-06-22  4:26 ` Gagandeep Singh
2022-06-23 14:08   ` Kevin Traynor
2022-06-22  4:47 ` Zhou, YidingX
2022-06-22  8:40   ` Kalesh Anakkur Purayil
2022-06-22 10:48 ` Niklas Söderlund
2022-06-24 14:17   ` Kevin Traynor
     [not found] ` <62b2851c.1c69fb81.cf480.7398SMTPIN_ADDED_BROKEN@mx.google.com>
2022-06-23 14:05   ` Kevin Traynor
2022-05-10 13:00 Kevin Traynor

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