patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	Chas Williams <chas3@att.com>, Chenbo Xia <chenbo.xia@intel.com>,
	Chengwen Feng <fengchengwen@huawei.com>,
	David Marchand <david.marchand@redhat.com>,
	Huisong Li <lihuisong@huawei.com>,
	Joshua Washington <joshwash@google.com>,
	Junfeng Guo <junfeng.guo@intel.com>,
	Lingli Chen <linglix.chen@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Maxime Gouin <maxime.gouin@6wind.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Olivier Matz <olivier.matz@6wind.com>,
	Praveen Kaligineedi <pkaligineedi@google.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Xiaoyun Li <xiaoyun.li@intel.com>
Subject: please help backporting some patches to stable release 22.11.8
Date: Mon, 17 Feb 2025 17:13:24 +0000	[thread overview]
Message-ID: <20250217171326.1069702-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 2025/02/24.

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

---
4dc4e33ffa  Olivier Matz     net/virtio: fix Rx checksum calculation
a71168a775  Praveen Kaligineedi net/gve: allocate Rx QPL pages using malloc
eb29e625ce  Stephen Hemminger test/bonding: fix active backup receive test

                 reply	other threads:[~2025-02-17 17:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250217171326.1069702-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=chas3@att.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=fengchengwen@huawei.com \
    --cc=humin29@huawei.com \
    --cc=joshwash@google.com \
    --cc=junfeng.guo@intel.com \
    --cc=lihuisong@huawei.com \
    --cc=linglix.chen@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=maxime.gouin@6wind.com \
    --cc=olivier.matz@6wind.com \
    --cc=pkaligineedi@google.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=xiaoyun.li@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).