patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: dpdk stable <stable@dpdk.org>, Luca Boccassi <luca.boccassi@gmail.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
	Chengwen Feng <fengchengwen@huawei.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	"David Hunt" <david.hunt@intel.com>,
	Gregory Etelson <getelson@nvidia.com>,
	"Kevin Laatz" <kevin.laatz@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>,
	Matan Azrad <matan@nvidia.com>,
	Michael Baum <michaelba@nvidia.com>,
	Reshma Pattan <reshma.pattan@intel.com>,
	"Sivaprasad Tummala" <sivaprasad.tummala@amd.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Tim Martin" <timothym@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	 Xiaoyu Min <jackmin@nvidia.com>
Subject: Re: please help backporting some patches to stable release 22.11.7
Date: Wed, 20 Nov 2024 17:32:47 +0800	[thread overview]
Message-ID: <255d99dd-a118-1967-b8f3-7fbafa10b690@huawei.com> (raw)
In-Reply-To: <20241112222355.669451-1-luca.boccassi@gmail.com>

Hi Luca,

The following patch can backport to 22.11 branch without any conflicts. 
Can you try it again?

0bc4795d59  Huisong Li       examples/l3fwd-power: fix options parsing overflow

/Huisong


在 2024/11/13 6:23, luca.boccassi@gmail.com 写道:
> 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 11/19/24.
>
> 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
>
> ---
> d46f3b525a  Gregory Etelson  net/mlx5: fix error notifications in counter initialization
> ee76b173b2  Gregory Etelson  net/mlx5: fix non-template flow action validation
> 0bc4795d59  Huisong Li       examples/l3fwd-power: fix options parsing overflow
> 2a682d65f8  Stephen Hemminger app/dumpcap: use bitops API instead of compiler builtins
> 27918f0d53  Tim Martin       net/mlx5: fix real time counter reading from PCI BAR
> .

  parent reply	other threads:[~2024-11-20  9:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 22:23 luca.boccassi
2024-11-12 22:51 ` Stephen Hemminger
2024-11-20  9:32 ` lihuisong (C) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-20 23:45 luca.boccassi
2024-10-23 21:31 luca.boccassi
2024-10-24  9:53 ` Richardson, Bruce
2024-10-24 23:59 ` Stephen Hemminger
2024-11-11 11:35 ` Robin Jarry
2024-11-12  8:59 ` David Marchand

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=255d99dd-a118-1967-b8f3-7fbafa10b690@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dsosnowski@nvidia.com \
    --cc=fengchengwen@huawei.com \
    --cc=getelson@nvidia.com \
    --cc=jackmin@nvidia.com \
    --cc=kevin.laatz@intel.com \
    --cc=konstantin.ananyev@huawei.com \
    --cc=luca.boccassi@gmail.com \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=reshma.pattan@intel.com \
    --cc=sivaprasad.tummala@amd.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=timothym@nvidia.com \
    --cc=viacheslavo@nvidia.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).