patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Huisong Li <lihuisong@huawei.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dpdk stable <stable@dpdk.org>, Xiaoyun Li <xiaoyun.li@intel.com>
Subject: Re: [dpdk-stable] "app/testpmd: verify DCB config during forward config" is incompatible with the 19.11.x series
Date: Fri, 4 Jun 2021 09:52:40 +0800	[thread overview]
Message-ID: <a26c8458-617c-35ac-8c2a-ae79ec0f2cd7@huawei.com> (raw)
In-Reply-To: <CAATJJ0LcXFFPYZXtHLSoaeQio83L0sEwjePN+xfrnkHh9_KfSA@mail.gmail.com>


在 2021/6/1 19:24, Christian Ehrhardt 写道:
> Hi,
> this commit was targted at the stable series:
>
> commit 43f1f8261136852357057b78aa49d354beaf3931
> Author: Huisong Li <lihuisong@huawei.com>
> Date:   Wed Apr 28 14:40:44 2021 +0800
>
>      app/testpmd: verify DCB config during forward config
The above patch does not need to be applied to 19.11.x, it is ok.
> As part of that it removes pt_id as it was the last user.
> But this does not work out without the following also in place.
>
> commit 08dcd187068666c96e8a16604a1c96160ed310e9
> Author: Huisong Li <lihuisong@huawei.com>
> Date:   Wed Dec 2 20:48:55 2020 +0800
>
>      app/testpmd: fix queue stats mapping configuration
>
> Since the latter is rather massive I have for now dropped 43f1f8261
> from the queue for 19.11.9.
> Please consider creating a backport or letting me know that this change
> isn't meant to be applied to 19.11.x
>
BTW, the first patch does not conflict if the second patch is applied to 
19.11.x first.

  reply	other threads:[~2021-06-04  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 11:24 Christian Ehrhardt
2021-06-04  1:52 ` Huisong Li [this message]
2021-06-04  5:01   ` Christian Ehrhardt
2021-06-04  6:35     ` Huisong Li

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=a26c8458-617c-35ac-8c2a-ae79ec0f2cd7@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=stable@dpdk.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).