All of lore.kernel.org
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk dev <dev@dpdk.org>
Cc: dpdk stable <stable@dpdk.org>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Anurag Mandal <anurag.mandal@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Ciara Loftus <ciara.loftus@intel.com>,
	Claudia Cauli <claudiacauli@gmail.com>,
	Dakota Sicher <dakota.sicher@broadcom.com>,
	David Marchand <david.marchand@redhat.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Jian Wang <jianwang@trustnetic.com>,
	Jiawen Wu <jiawenwu@trustnetic.com>,
	Junfeng Guo <junfengg@nvidia.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	Marat Khalili <marat.khalili@huawei.com>,
	Maxime Peim <maxime.peim@gmail.com>,
	Mingjin Ye <mingjinx.ye@intel.com>,
	Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ting Xu <ting.xu@intel.com>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Xiaoyun Li <xiaoyun.li@intel.com>,
	Zaiyu Wang <zaiyuwang@trustnetic.com>
Subject: please help backporting some patches to stable release 24.11.7
Date: Mon,  6 Jul 2026 11:27:26 +0100	[thread overview]
Message-ID: <20260706102728.29680-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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2026/07/10.

You can find the a temporary work-in-progress branch of the coming 24.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 24.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
ece7d7eef0  Anurag Mandal    net/iavf: fix duplicate VF reset during PF reset recovery
8e038dee42  Bruce Richardson net/idpf: fix Tx of large mbuf segments
edff93f638  Dakota Sicher    net/bnxt: skip timed Tx pacing setup when unsupported
1c39f3f240  Marat Khalili    bpf/validate: fix BPF_JMP empty range handling
7f8ce8d13f  Marat Khalili    bpf/validate: fix EBPF_JSLT | BPF_X evaluation
b482a764c6  Maxime Peim      eal: fix index for non-EAL lcores
26e7538e00  Zaiyu Wang       net/txgbe: fix link flow control config for Sapphire
e586adbac0  Zaiyu Wang       net/txgbe: fix mass of unknown interrupts

             reply	other threads:[~2026-07-06 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 10:27 luca.boccassi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-13 17:22 please help backporting some patches to stable release 24.11.7 luca.boccassi

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=20260706102728.29680-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=anurag.mandal@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=claudiacauli@gmail.com \
    --cc=dakota.sicher@broadcom.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianwang@trustnetic.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=junfengg@nvidia.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=marat.khalili@huawei.com \
    --cc=maxime.peim@gmail.com \
    --cc=mingjinx.ye@intel.com \
    --cc=mohammad-shuab.siddique@broadcom.com \
    --cc=qi.z.zhang@intel.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=ting.xu@intel.com \
    --cc=vladimir.medvedkin@intel.com \
    --cc=xiaoyun.li@intel.com \
    --cc=zaiyuwang@trustnetic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.