patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: "lihuisong (C)" <lihuisong@huawei.com>,
	Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 21.11.3
Date: Fri, 9 Dec 2022 06:06:43 +0000	[thread overview]
Message-ID: <BYAPR11MB27111D277FE2F5327F9B4F8EFE1C9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3ab351b6-96f7-74bc-7002-d6927fe23651@redhat.com>

Hi Huisong,

21.11.3-rc1 also meet this issue https://bugs.dpdk.org/show_bug.cgi?id=1118, please backporting related patches to stable21.11. Thanks
Notes:
    Apply patch: https://patches.dpdk.org/project/dpdk/patch/20221031131744.2340150-1-ivan.malov@oktetlabs.ru/ on LTS dpdk-21.11.3-rc1,
    test passed.

Best regards,
Yu Jiang

> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Wednesday, November 30, 2022 5:52 PM
> To: lihuisong (C) <lihuisong@huawei.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: Re: please help backporting some patches to stable release 21.11.3
> 
> On 30/11/2022 08:18, lihuisong (C) wrote:
> >
> > 在 2022/11/24 2:06, Kevin Traynor 写道:
> >> 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 21.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 21.11 branch, or
> >>       - Indicate that the patch should not be backported
> >>
> >> Please do either of the above by 11/29/22.
> >>
> >> You can find the a temporary work-in-progress branch of the coming
> >> 21.11.3 release at:
> >>       https://github.com/kevintraynor/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=d90e6ae6f936ecdc2
> >> fd3811ff9f26aec7f3c06eb
> >>
> >> When sending the backported patch, please indicate the target branch
> >> in the subject line, as we have multiple branches, for example:
> >>       [PATCH 21.11] foo/bar: fix baz
> >>
> >> With git format-patch, this can be achieved by appending the parameter:
> >>       --subject-prefix='PATCH 21.11'
> >>
> >> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> >>
> >> FYI, branch 21.11 is located at tree:
> >>      https://git.dpdk.org/dpdk-stable
> >>
> >> Thanks.
> >>
> >> Kevin
> >>
> >> ---
> >> d4cbbee345  David Marchand   trace: fix metadata dump
> >> 5a0f64d84b  Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx
> queues
> >> 59ceaa72d5  Harman Kalra     common/cnxk: fix part number for CN10K
> >> b4924c0db5  Huisong Li       net/bonding: fix mbuf fast free handling
> >> a35799625e  Huisong Li       net/hns3: fix lock protection of RSS flow rule
> >> 1042ed401f  Huisong Li       net/hns3: fix restore filter function input
> >> 0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
> >
> > Hi Kervin,
> >
> > These comit-ids:a35799625e, 1042ed401f and 0d81da2559 have been sent
> > to 21.11.
> >
> > Do I need to resend?
> >
> 
> Hi Huisong,
> 
> No need to resend, they are in queue now and will be pushed after CI.
> b4924c0db5 is also pushed. It seems the mail was not using the very latest list. I
> will resend the list. Thanks for email to confirm on patches and apologies.
> 
> Kevin.
> 
> >> 3e13a6ae95  Jiawei Wang      net/mlx5: fix mirror flow validation with ASO
> action
> >> e9de8f33ca  Jiawei Wang      net/mlx5: fix source port checking in sample
> flow rule
> >> 16d6ebb65d  Kai Ji           crypto/ipsec_mb: fix null checks
> >> ef4ece4dbb  Michael Baum     net/mlx5: fix port closing
> >> 13c5c09390  Michael Baum     net/mlx5: fix port event cleaning order
> >> a94e89e47b  Michael Baum     net/mlx5: fix race condition in counter pool
> resizing
> >> e77d682aad  Nicolas Chautru  baseband/acc100: fix input error related
> >> to padding
> >> 5781638519  Nithin Dabilpuram common/cnxk: fix RQ mask config for
> >> CN10KB chip 3fe71706ab  Pavan Nikhilesh  event/cnxk: fix stale data
> >> in workslot
> >> 927cb43fe9  Pavan Nikhilesh  examples/l3fwd: fix port group mask with
> AltiVec
> >> afb98009a0  Shun Hao         net/mlx5: fix assert when creating meter policy
> >> 3b6d78bb8e  Shun Hao         net/mlx5: fix meter policy with port ID
> destination
> >> 0f3ba0d4a8  Spike Du         net/mlx5: fix testpmd quit with available desc
> threshold
> >> 21dc24b746  Stephen Hemminger ring: remove leftover comment about
> watermark
> >> 0f044b6681  Steve Yang       net/iavf: fix refine protocol header
> >> 0b241667cc  Steve Yang       net/iavf: fix tainted scalar
> >> b125c0e721  Steve Yang       net/iavf: fix tainted scalar
> >> cb5c1b91f7  Yiding Zhou      net/iavf: add thread for event callbacks
> >> a774cba0bb  Yogesh Jangra    pipeline: fix validate header instruction
> >>
> >> .
> >


  reply	other threads:[~2022-12-09  6:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 18:06 Kevin Traynor
2022-11-24  8:01 ` Michael Baum
2022-11-24 17:02 ` Ji, Kai
2022-11-29 12:55   ` Kevin Traynor
2022-11-28  9:24 ` Spike Du
2022-11-29 12:59   ` Kevin Traynor
2022-11-28  9:28 ` Shun Hao
2022-11-29 13:06   ` Kevin Traynor
2022-11-30  8:18 ` lihuisong (C)
2022-11-30  9:51   ` Kevin Traynor
2022-12-09  6:06     ` Jiang, YuX [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-30 10:02 Kevin Traynor
2022-11-11 18:44 Kevin Traynor
2022-10-25 15:35 Kevin Traynor

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=BYAPR11MB27111D277FE2F5327F9B4F8EFE1C9@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=lihuisong@huawei.com \
    --cc=stable@dpdk.org \
    /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).