From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Gavin Li <gavinl@nvidia.com>,
Bruce Richardson <bruce.richardson@intel.com>,
David Marchand <david.marchand@redhat.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Oleksandr Nahnybida <oleksandrn@interfacemasters.com>,
Robin Jarry <rjarry@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Sunil Kumar Kori <skori@marvell.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Zerun Fu <zerun.fu@corigine.com>
Subject: please help backporting some patches to stable release 22.11.7
Date: Wed, 23 Oct 2024 22:31:52 +0100 [thread overview]
Message-ID: <20241023213154.1231303-1-luca.boccassi@gmail.com> (raw)
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/10/30.
You can find the a temporary work-in-progress branch of the coming 22.11.7
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
---
d16364e3bd Bruce Richardson common/idpf: fix AVX-512 pointer copy on 32-bit
b34fe66ea8 Bruce Richardson net/iavf: delay VF reset command
f665790a5d David Marchand drivers: remove redundant newline from logs
e4a4087992 Gavin Li net/mlx5: set errno for ipool allocation failures
6c3de40af8 Nithin Dabilpuram common/cnxk: fix inline CTX write
6db358536f Oleksandr Nahnybida pcapng: fix handling of chained mbufs
6f96937dad Robin Jarry ethdev: fix race on ports in telemetry endpoints
4baf54ed9d Stephen Hemminger common/idpf: fix use after free in mailbox init
2d4505dc6d Sunil Kumar Kori common/cnxk: fix MAC address change with active VF
b04b06f4cb Viacheslav Ovsiienko net/mlx5: fix flex item header length field translation
97e19f0762 Viacheslav Ovsiienko net/mlx5: fix non full word sample fields in flex item
2254813795 Zerun Fu net/nfp: notify flower firmware about PF speed
next reply other threads:[~2024-10-23 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 21:31 luca.boccassi [this message]
2024-10-24 9:53 ` Richardson, Bruce
2024-10-24 23:59 ` Stephen Hemminger
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=20241023213154.1231303-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=gavinl@nvidia.com \
--cc=ndabilpuram@marvell.com \
--cc=oleksandrn@interfacemasters.com \
--cc=rjarry@redhat.com \
--cc=skori@marvell.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=viacheslavo@nvidia.com \
--cc=zerun.fu@corigine.com \
/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).