From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4 00/36] update for i40e base code
Date: Tue, 4 Feb 2020 11:23:20 +0800 [thread overview]
Message-ID: <20200204032320.GN54838@intel.com> (raw)
In-Reply-To: <5f6b078d-23c5-0970-2d82-b512da8fb752@redhat.com>
Hi, Kevin
On 02/03, Kevin Traynor wrote:
>On 13/01/2020 05:59, Ye, Xiaolong wrote:
[snip]
>>> -----Original Message-----
>Hi Xiaolong/Beilei/Qi Z,
>
>Some of these patches are tagged to go to 'S'table and are 'F'ixes,
>while others are also fixes for older releases but not tagged to go to
>stable.
>
>No issue with not backporting patches (in fact i would prefer not if
>some doubts), but want to check if the stable tag was missed by accident?
>
>Also, note that Fw listed is v6.01 for 18.11, (v7.00 for 19.11) so
>changes would need to be compatible with that.
Yes, some of the stable tags were missed deliberately since the new base code
update is for FW 7.1/7.2, it's not guaranteed to be compatible with old FW.
>
>20.02 8f33cbcfa S F net/i40e/base: fix buffer address (16.04)
>20.02 4b3da9415 S F net/i40e/base: fix error message (1.7.0)
>20.02 1da546c39 - F net/i40e/base: fix missing link modes (17.08)
>20.02 79bfe7808 S F net/i40e/base: fix Tx descriptors number (1.7.0)
>20.02 50126939c - F net/i40e/base: fix retrying logic (18.02)
>20.02 b330a1c5c - F net/i40e/base: fix display of FEC settings (17.08)
>20.02 03ef7d47f - F net/i40e/base: add new link speed constants (17.08)
>
I would suggest we only backport below obvious fixes to stable releases.
20.02 8f33cbcfa S F net/i40e/base: fix buffer address (16.04)
20.02 4b3da9415 S F net/i40e/base: fix error message (1.7.0)
20.02 79bfe7808 S F net/i40e/base: fix Tx descriptors number (1.7.0)
20.02 50126939c - F net/i40e/base: fix retrying logic (18.02)
Thanks,
Xiaolong
>Please confirm on patches above missing stable tag. For time being I
>will only consider ones with stable tag.
>
>thanks,
>Kevin.
>
next prev parent reply other threads:[~2020-02-04 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191202074935.97629-1-xiaolong.ye@intel.com>
[not found] ` <20200113023949.26718-1-xiaolong.ye@intel.com>
[not found] ` <94479800C636CB44BD422CB454846E013CEC8CCD@SHSMSX101.ccr.corp.intel.com>
[not found] ` <008b5b10198142fe92d08cd9f5bf1b33@intel.com>
2020-02-03 14:09 ` Kevin Traynor
2020-02-04 3:23 ` Ye Xiaolong [this message]
2020-02-07 9:36 ` 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=20200204032320.GN54838@intel.com \
--to=xiaolong.ye@intel.com \
--cc=beilei.xing@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=qi.z.zhang@intel.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).