From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Subject: [dpdk-stable] Fwd: please help backporting some patches to stable release 20.11.2
Date: Thu, 13 May 2021 11:18:02 +0100 [thread overview]
Message-ID: <28797869-b83a-fba8-5c85-8527e4107ac4@intel.com> (raw)
In-Reply-To: <20210510224153.31477-1-xuemingl@nvidia.com>
Initial mail is not in the mail list, forwarding to mail list again for archive.
-------- Forwarded Message --------
Subject: please help backporting some patches to stable release 20.11.2
Date: Tue, 11 May 2021 06:41:53 +0800
From: Xueming Li <xuemingl@nvidia.com>
Hi commit authors (and maintainers),
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 05/17/21.
You can find the a temporary work-in-progress branch of the coming 20.11.2
release at:
https://github.com/steevenlee/dpdk
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.
Xueming Li <xuemingl@nvidia.com>
---
1e28e842e0 Chengchang Tang net/hns3: fix imprecise statistics
d566bfcff0 Chengchang Tang net/hns3: fix timing in mailbox
ec2ed976ac Chengwen Feng net/hns3: delete mailbox arq ring
c8dec72de0 Chengwen Feng net/hns3: fix possible mismatched response of mailbox
55c038c2db Chengwen Feng net/hns3: fix PTP capability report
76a3836b98 Chengwen Feng net/hns3: fix setting default MAC address in
bonding of VF
e40ad6fca4 Chengwen Feng net/hns3: fix verification of NEON support
dbbbad23e3 Chengwen Feng net/hns3: fix VF handling LSC event in secondary
process
aa5baf47e1 Chengwen Feng net/hns3: rename Rx burst function
c53a5f3efb Chengwen Feng telemetry: check thread creations
3cd7290c16 David Marchand ci: catch coredumps
631217c761 Elad Nachman kni: fix kernel deadlock with bifurcated device
f9f24ecd79 Hongbo Zheng net/hns3: fix concurrent interrupt handling
a2258ea1be Huisong Li doc: remove queue stats mapping from testpmd guide
fdfde7a4a0 Huisong Li net/hns3: fix mbuf leakage
23abee9dea Ilya Maximets net/virtio: fix interrupt unregistering for
listening socket
d8caafcbf9 Ivan Malov net/sfc: fix outer rule and encap rollback on error
8f5ea6a464 Juraj Linkeš config/arm: fix implementer and its SoCs
53f98141ee Kalesh AP net/bnxt: fix PTP support for Thor
25fefa2b17 Lance Richardson net/bnxt: fix Rx descriptor status
9f13e888ef Lance Richardson net/bnxt: fix Rx queue count
e6988afdc7 Matan Azrad net/mlx5: fix imissed statistics
8e321f7df1 Min Hu (Connor) doc: fix Rx burst function in hns3 guide
53ef1b3477 Min Hu (Connor) ethdev: add sanity checks in control APIs
052a5d3867 Pavan Nikhilesh event/octeontx2: fix XAQ pool reconfigure
83306d6c46 Shun Hao net/mlx5: fix meter statistics
487cfc2437 Thomas Monjalon app: fix exit messages
204a7f44bc Thomas Monjalon bus/pci: support I/O port operations with musl
d61381ad46 Viacheslav Ovsiienko net/mlx5: support timestamp format
dd25bd201d Viacheslav Ovsiienko regex/mlx5: support timestamp format
687833fffa Wei Huang raw/ifpga/base: check size before assigning
f2cb939365 Wisam Jaddo app/flow-perf: fix IPv6 source address increment
prev parent reply other threads:[~2021-05-13 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210510224153.31477-1-xuemingl@nvidia.com>
2021-05-11 6:43 ` [dpdk-stable] " Elad Nachman
2021-05-11 11:43 ` Xueming(Steven) Li
2021-05-11 9:34 ` David Marchand
2021-05-11 10:36 ` Luca Boccassi
2021-05-11 11:25 ` David Marchand
2021-05-11 14:44 ` Aaron Conole
2021-05-11 23:41 ` Xueming(Steven) Li
2021-05-11 11:18 ` Thomas Monjalon
2021-05-13 10:18 ` Ferruh Yigit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28797869-b83a-fba8-5c85-8527e4107ac4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).