patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Chaoyong He" <chaoyong.he@corigine.com>,
	"Chenbo Xia" <chenbo.xia@intel.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Eelco Chaudron" <echaudro@redhat.com>,
	"Gavin Hu" <gavin.hu@arm.com>,
	"Heinrich Kuhn" <heinrich.kuhn@corigine.com>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Ivan Malov" <ivan.malov@oktetlabs.ru>,
	"Jianfeng Tan" <jianfeng.tan@intel.com>,
	"Jiayu Hu" <hujiayu.hu@foxmail.com>,
	"Jiayu Hu" <jiayu.hu@intel.com>,
	"Kumara Parameshwaran" <kumaraparamesh92@gmail.com>,
	"Long Wu" <long.wu@corigine.com>,
	"Maxime Coquelin" <maxime.coquelin@redhat.com>,
	"Nathan Brown" <nathan.brown@arm.com>,
	"Niklas Söderlund" <niklas.soderlund@corigine.com>,
	"Ola Liljedahl" <ola.liljedahl@arm.com>,
	"Peng Zhang" <peng.zhang@corigine.com>,
	"Ruifeng Wang" <ruifeng.wang@arm.com>,
	"Simon Horman" <simon.horman@corigine.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Tiwei Bie" <tiwei.bie@intel.com>,
	"Tyler Retzlaff" <roretzla@linux.microsoft.com>
Subject: please help backporting some patches to stable release 22.11.5
Date: Thu,  7 Mar 2024 01:38:34 +0000	[thread overview]
Message-ID: <20240307013843.1737311-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 03/14/24.

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

---
8b8f116b19  Chaoyong He      net/nfp: fix resource leak for CoreNIC firmware
66d5f53d3e  Chaoyong He      net/nfp: fix resource leak for exit of CoreNIC firmware
a256a1227d  Chaoyong He      net/nfp: fix resource leak for exit of flower firmware
7c596721ae  Chaoyong He      net/nfp: fix resource leak for flower firmware
b3e42d9236  David Marchand   vhost: fix virtqueue access check in vhost-user setup
df33fb53e4  Honnappa Nagarahalli rcu: fix acked token in debug log
063cddfc74  Honnappa Nagarahalli rcu: use atomic operation on acked token
547f294357  Kumara Parameshwaran gro: fix reordering of packets
243bbfa0f9  Long Wu          net/nfp: fix device close
09309f8735  Long Wu          net/nfp: fix device resource freeing
20eaa8e2eb  Long Wu          net/nfp: free switch domain ID on close
323b626a86  Stephen Hemminger net/sfc: fix compile-time check

             reply	other threads:[~2024-03-07  1:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  1:38 luca.boccassi [this message]
2024-03-14  0:17 luca.boccassi
2024-03-18 15:41 luca.boccassi
2024-03-25 12:18 luca.boccassi
2024-03-28 17:27 luca.boccassi
2024-03-28 17:31 ` Gregory Etelson

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=20240307013843.1737311-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=chaoyong.he@corigine.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=echaudro@redhat.com \
    --cc=gavin.hu@arm.com \
    --cc=heinrich.kuhn@corigine.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=hujiayu.hu@foxmail.com \
    --cc=ivan.malov@oktetlabs.ru \
    --cc=jianfeng.tan@intel.com \
    --cc=jiayu.hu@intel.com \
    --cc=kumaraparamesh92@gmail.com \
    --cc=long.wu@corigine.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nathan.brown@arm.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=ola.liljedahl@arm.com \
    --cc=peng.zhang@corigine.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=ruifeng.wang@arm.com \
    --cc=simon.horman@corigine.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=tiwei.bie@intel.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).