patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 20.11.8
@ 2023-03-29  1:05 luca.boccassi
  0 siblings, 0 replies; 9+ messages in thread
From: luca.boccassi @ 2023-03-29  1:05 UTC (permalink / raw)
  To: dpdk stable
  Cc: Beilei Xing, Bernard Iremonger, Ferruh Yigit, Michael Baum,
	Ori Kam, Wenzhuo Lu

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

Please do either of the above by 31/03/23.

You can find the a temporary work-in-progress branch of the coming 20.11.8
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
7bdf7a13ae  Michael Baum     app/testpmd: fix encap/decap size calculation

^ permalink raw reply	[flat|nested] 9+ messages in thread
* please help backporting some patches to stable release 20.11.8
@ 2023-03-22  0:43 luca.boccassi
  0 siblings, 0 replies; 9+ messages in thread
From: luca.boccassi @ 2023-03-22  0:43 UTC (permalink / raw)
  To: dpdk stable
  Cc: Andrew Rybchenko, Andy Moreton, Chenbo Xia, David Marchand,
	Dukai Yuan, Harman Kalra, Hyong Youb Kim, Igor Romanov,
	Ivan Malov, Ivan Malov, Jianfeng Tan, Junjie Chen,
	Maxime Coquelin

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

Please do either of the above by 28/03/23.

You can find the a temporary work-in-progress branch of the coming 20.11.8
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
7995bf4c29  David Marchand   net/vhost: fix Rx interrupt
723327bed4  Ivan Malov       net/sfc: invalidate switch port entry on representor unplug

^ permalink raw reply	[flat|nested] 9+ messages in thread
* please help backporting some patches to stable release 20.11.8
@ 2023-03-15 22:49 luca.boccassi
  2023-03-21  9:37 ` lihuisong (C)
  0 siblings, 1 reply; 9+ messages in thread
From: luca.boccassi @ 2023-03-15 22:49 UTC (permalink / raw)
  To: dpdk stable
  Cc: Anatoly Burakov, Beilei Xing, Bernard Iremonger, Chengchang Tang,
	Chengwen Feng, Chunsong Feng, Dmitry Kozlyuk, Dongdong Liu,
	Ferruh Yigit, Ferruh Yigit, Gerry Gribbon, Hao Chen, Huisong Li,
	Lijun Ou, Matan Azrad, Michael Baum, Min Hu (Connor),
	Ori Kam, Shahaf Shuler, Shiyang He, Tal Shnaiderman,
	Thomas Monjalon, Tyler Retzlaff, Viacheslav Ovsiienko,
	Wei Hu (Xavier),
	Wenzhuo Lu, Yisen Zhuang

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

Please do either of the above by 22/03/23.

You can find the a temporary work-in-progress branch of the coming 20.11.8
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
8e9bd29995  Chengwen Feng    net/hns3: fix empty devargs parsing
b15d75b287  Gerry Gribbon    regex/mlx5: fix doorbell record
eb3ef9e0d7  Huisong Li       net/hns3: add verification of RSS types
e3069658da  Huisong Li       net/hns3: reimplement hash flow function
5028f207a4  Shiyang He       app/testpmd: fix secondary process packet forwarding

^ permalink raw reply	[flat|nested] 9+ messages in thread
* please help backporting some patches to stable release 20.11.8
@ 2023-02-23  9:42 luca.boccassi
  2023-03-01 16:15 ` Kundapura, Ganapati
  2023-03-21  9:29 ` lihuisong (C)
  0 siblings, 2 replies; 9+ messages in thread
From: luca.boccassi @ 2023-02-23  9:42 UTC (permalink / raw)
  To: dpdk stable
  Cc: Abhinandan Gujjar, Akhil Goyal, Alexander Kozyrev, Aman Singh,
	Beilei Xing, Bernard Iremonger, Bruce Richardson,
	Chengchang Tang, Chengwen Feng, David Christensen, Dongdong Liu,
	Ferruh Yigit, Gage Eads, Ganapati Kundapura, Hongbo Zheng,
	Huisong Li, Jerin Jacob, Konstantin Ananyev, Lijun Ou,
	Matan Azrad, Michael Qiu, Min Hu (Connor),
	Neil Horman, Nelio Laranjeiro, Nikhil Rao, Pablo de Lara,
	Ray Kinsella, Ruifeng Wang, Shahaf Shuler, Suanming Mou,
	Viacheslav Ovsiienko, Wei Hu (Xavier),
	Wenzhuo Lu, Yisen Zhuang, Yongseok Koh

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

Please do either of the above by 02/03/23.

You can find the a temporary work-in-progress branch of the coming 20.11.8
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
1f903ebe2c  Alexander Kozyrev net/mlx5: check compressed CQE opcode in vectorized Rx
27fd465215  Chengwen Feng    net/hns3: declare flow rule keeping capability
cdede073a5  Ferruh Yigit     app/testpmd: fix link check condition on port start
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
52a4e960b4  Huisong Li       net/hns3: extract common function to query device
10f91af5a5  Huisong Li       net/hns3: fix burst mode query with dummy function
2aec7beaba  Huisong Li       net/hns3: make getting Tx function static
a8d240786e  Huisong Li       net/hns3: remove debug condition for Tx prepare
6a934ba4c6  Huisong Li       net/hns3: separate Tx prepare from getting Tx function
cedb44dc87  Suanming Mou     common/mlx5: improve AES-XTS tweak capability check
9b31fc9007  Viacheslav Ovsiienko net/mlx5: fix read device clock in real time mode

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

end of thread, other threads:[~2023-03-29  1:05 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-29  1:05 please help backporting some patches to stable release 20.11.8 luca.boccassi
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22  0:43 luca.boccassi
2023-03-15 22:49 luca.boccassi
2023-03-21  9:37 ` lihuisong (C)
2023-02-23  9:42 luca.boccassi
2023-03-01 16:15 ` Kundapura, Ganapati
2023-03-02  9:47   ` Luca Boccassi
2023-03-02 10:18     ` Kundapura, Ganapati
2023-03-21  9:29 ` lihuisong (C)

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