patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: dpdk stable <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 19.11.14
Date: Tue, 22 Nov 2022 10:57:25 +0000	[thread overview]
Message-ID: <ee70e92f-b11d-361c-5e40-4ede46fd0eef@ericsson.com> (raw)
In-Reply-To: <20221116104124.2975325-1-christian.ehrhardt@canonical.com>

On 2022-11-16 11:41, christian.ehrhardt@canonical.com wrote:
> 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 19.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 19.11 branch, or
>      - Indicate that the patch should not be backported
> 
> Please do either of the above by 11/23/22.
> 
> You can find the a temporary work-in-progress branch of the coming 19.11.14
> release at:
>      https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-e75f0bbe085339d0&q=1&e=0607c67f-dbb5-4191-98c7-5b2591400d76&u=https%3A%2F%2Fgithub.com%2Fcpaelzer%2Fdpdk-stable-queue
> 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://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-635cd7039f493ff2&q=1&e=0607c67f-dbb5-4191-98c7-5b2591400d76&u=https%3A%2F%2Fgit.dpdk.org%2Fdpdk-stable%2Fcommit%2F%3Fh%3D18.11%26id%3Dd90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
> 
> When sending the backported patch, please indicate the target branch in the
> subject line, as we have multiple branches, for example:
>      [PATCH 19.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>      --subject-prefix='PATCH 19.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 19.11 is located at tree:
>     https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-69822621fdd11bcf&q=1&e=0607c67f-dbb5-4191-98c7-5b2591400d76&u=https%3A%2F%2Fgit.dpdk.org%2Fdpdk-stable
> 
> Thanks.
> 
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
> 
> ---
> da4470cb17  Alexander Kozyrev net/mlx5: fix first segment inline length
> 63bd264485  Frank Du         net/ice: fix interrupt handler unregister
> 236bc417e2  Gregory Etelson  app/testpmd: fix MAC header in checksum forward engine
> b9f1f4c239  Gregory Etelson  net/mlx5: fix port initialization with small LRO
> a2248c87e2  Haiyue Wang      ring: fix description
> b514566778  Huisong Li       net/bonding: fix slave device Rx/Tx offload configuration
> 4109d71e52  Mattias Rönnblom doc: fix event timer adapter guide

4109d71e52 needs not be backported, imo.

> 13c5c09390  Michael Baum     net/mlx5: fix port event cleaning order


       reply	other threads:[~2022-11-22 10:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221116104124.2975325-1-christian.ehrhardt@canonical.com>
2022-11-22 10:57 ` Mattias Rönnblom [this message]
2022-11-22 11:35   ` Christian Ehrhardt
     [not found] <20221111114803.1553104-1-christian.ehrhardt@canonical.com>
2022-12-01  4:11 ` lihuisong (C)
2022-12-01  6:36   ` Christian Ehrhardt
     [not found] <20221111114814.1553136-1-christian.ehrhardt@canonical.com>
2022-11-14  9:57 ` Nicolau, Radu
2022-11-17  8:17   ` 答复: " Mao,Yingming
2022-11-17  8:19     ` Christian Ehrhardt
2022-11-16 10:45 ` Morten Brørup
2022-11-17  6:27   ` Christian Ehrhardt
2022-11-17  7:25     ` Christian Ehrhardt
2022-11-16 23:23 ` Mah, Yock Gen
2022-11-17  8:49   ` Christian Ehrhardt
2022-11-17 14:33 ` Niklas Soderlund

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=ee70e92f-b11d-361c-5e40-4ede46fd0eef@ericsson.com \
    --to=mattias.ronnblom@ericsson.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).