DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	dev@dpdk.org, "Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH V1] doc: update recommended kernel version for i40e
Date: Wed, 15 Jan 2020 10:29:06 +0800	[thread overview]
Message-ID: <20200115022906.GD33538@intel.com> (raw)
In-Reply-To: <6f2159b8-e118-3a50-e9e2-8e00a01b972a@redhat.com>

On 01/14, Kevin Traynor wrote:
>On 14/01/2020 19:10, Kevin Traynor wrote:
>> On 14/01/2020 02:28, Ye Xiaolong wrote:
>>> On 01/03, Chen, Zhaoyan wrote:
>>>> Update supported Intel NIC driver version and firmware version for 19.11
>>>> Update supported Intel NIC driver version to 2.8.43 for 19.08 which is 
>>>> widely tested
>>>>
>> 
>> This should be backported to 19.11 branch. Please add Cc:
>> stable@dpdk.org . Not sure which Fixed commit, if no code changes were
>> needed then suggest picking the commit that added the Intel testing
>> results in the release notes.
>> 
>
>Actually, this is the commit to use:
>
>Fixes: cb8a35c22aa9 ("doc: update supported i40e driver and firmware
>version")

Thanks for the reminder, I'll add Fixes tag and cc stable in next-net-intel tree.

Thanks,
Xiaolong
>
>>>> Signed-off-by: Zhaoyan Chen <zhaoyan.chen@intel.com>
>>>> ---
>>>> doc/guides/nics/i40e.rst | 4 +++-
>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
>>>> index 38acf5906..c7c34b62f 100644
>>>> --- a/doc/guides/nics/i40e.rst
>>>> +++ b/doc/guides/nics/i40e.rst
>>>> @@ -69,7 +69,9 @@ to chapter Tested Platforms/Tested NICs in release notes.
>>>>    +--------------+-----------------------+------------------+
>>>>    | DPDK version | Kernel driver version | Firmware version |
>>>>    +==============+=======================+==================+
>>>> -   |    19.08     |         2.9.21        |       7.00       |
>>>> +   |    19.11     |         2.9.21        |       7.00       |
>>>> +   +--------------+-----------------------+------------------+
>>>> +   |    19.08     |         2.8.43        |       7.00       |
>>>>    +--------------+-----------------------+------------------+
>>>>    |    19.05     |         2.7.29        |       6.80       |
>>>>    +--------------+-----------------------+------------------+
>>>> -- 
>>>> 2.22.0
>>>>
>>>
>>> Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>
>>>
>>> Applied to dpdk-next-net-intel, Thanks.
>>>
>> 
>

  reply	other threads:[~2020-01-15  2:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03  3:03 Chen, Zhaoyan
2020-01-14  2:28 ` Ye Xiaolong
2020-01-14 19:10   ` Kevin Traynor
2020-01-14 19:15     ` Kevin Traynor
2020-01-15  2:29       ` Ye Xiaolong [this message]
2021-04-19 22:01         ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2020-01-03  2:59 Chen, Zhaoyan
2020-01-03  2:54 Chen, Zhaoyan

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=20200115022906.GD33538@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=zhaoyan.chen@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).