patches for DPDK stable branches
 help / color / mirror / Atom feed
* [dpdk-stable] please help backporting some patches to stable release 19.11.6
@ 2020-11-09 19:05 luca.boccassi
       [not found] ` <20201109190556.3481033-1-luca.boccassi@gmail.com>
  0 siblings, 1 reply; 10+ messages in thread
From: luca.boccassi @ 2020-11-09 19:05 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

I didn't apply following commits from DPDK main to 19.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 19.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by the 16th of November.


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 19.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
0e98d5e6d9  Chengchang Tang  net/hns3: fix packet type report in Rx
f9edada651  Chengchang Tang  net/hns3: fix Tx checksum outer header prepare
fb6eb9009f  Chengchang Tang  net/hns3: fix Tx checksum with fixed header length
ead06572bd  Jesse Brandeburg net/iavf: fix performance with writeback policy
c59898131b  Maxime Coquelin  vhost: validate index in async API
364eb0e466  Nithin Dabilpuram net/octeontx2: avoid per packet barrier with multi segment
fb4b7a131c  Patrick Fu       vhost: fix guest/host physical address conversion
1cbdad1bf2  Xueming Li       common/mlx5: get number of ports that can be bonded

^ permalink raw reply	[flat|nested] 10+ messages in thread
* [dpdk-stable] please help backporting some patches to stable release 19.11.6
@ 2020-11-17 11:28 luca.boccassi
  0 siblings, 0 replies; 10+ messages in thread
From: luca.boccassi @ 2020-11-17 11:28 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

I didn't apply following commits from DPDK main to 19.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 19.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 11/24/20.


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 19.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
fe5d0e85b7  Chenxu Di        net/i40e: fix flow director flex configuration
992e6df3da  Jiawei Wang      common/mlx5: free MR resource on device DMA unmap

^ permalink raw reply	[flat|nested] 10+ messages in thread
* [dpdk-stable] please help backporting some patches to stable release 19.11.6
@ 2020-11-25  9:07 luca.boccassi
  0 siblings, 0 replies; 10+ messages in thread
From: luca.boccassi @ 2020-11-25  9:07 UTC (permalink / raw)
  To: dpdk stable

Hi commit authors (and maintainers),

I didn't apply following commits from DPDK main to 19.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 19.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by November 30th.


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 19.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
023b46db54  Harman Kalra     common/octeontx2: fix mbox response by syncing data types
5ea8356ec8  Tonghao Zhang    net/mlx5: check register available for metadata action

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

end of thread, other threads:[~2020-11-25  9:07 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20201102194256.1910550-1-luca.boccassi@gmail.com>
2020-11-02 19:43 ` [dpdk-stable] please help backporting some patches to stable release 19.11.6 luca.boccassi
2020-11-03  9:06   ` oulijun
2020-11-03 15:04 ` Ruifeng Wang
2020-11-04  8:42 ` Wangxiaoyun (Cloud)
2020-11-09 19:05 luca.boccassi
     [not found] ` <20201109190556.3481033-1-luca.boccassi@gmail.com>
2020-11-12  9:19   ` Fu, Patrick
2020-11-12  9:38     ` Luca Boccassi
2020-11-23  1:53   ` oulijun
2020-11-17 11:28 luca.boccassi
2020-11-25  9:07 luca.boccassi

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git