From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Zhang, RobinX" <robinx.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Guo, Junfeng" <junfeng.guo@intel.com>,
"Yang, SteveX" <stevex.yang@intel.com>,
"John McNamara" <john.mcnamara@intel.com>
Subject: Re: [PATCH v2] net/ice/base: support E824S and E825 devices
Date: Thu, 24 Feb 2022 11:37:49 +0000 [thread overview]
Message-ID: <4378bf32-d37b-de67-8ec5-ff9cd5080d2b@intel.com> (raw)
In-Reply-To: <34865f0acb034bf996faf4a4bd5f4a6f@intel.com>
On 2/23/2022 2:42 AM, Zhang, Qi Z wrote:
>
>
>> -----Original Message-----
>> From: Zhang, RobinX <robinx.zhang@intel.com>
>> Sent: Wednesday, February 16, 2022 3:45 PM
>> To: dev@dpdk.org
>> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z
>> <qi.z.zhang@intel.com>; Guo, Junfeng <junfeng.guo@intel.com>; Yang, SteveX
>> <stevex.yang@intel.com>; Zhang, RobinX <robinx.zhang@intel.com>
>> Subject: [PATCH v2] net/ice/base: support E824S and E825 devices
>>
>> Add support for E824S and E825 family devices.
>>
>> Signed-off-by: Robin Zhang <robinx.zhang@intel.com>
>
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
>
> Applied to dpdk-next-net-intel.
>
Hi Qi, Robin,
The apply note is on v2, but v1 seems merged to your tree,
omitting release notes update (which was the request on v1).
I guess you don't want to document it in release notes
since devices are still under test and it will be
documented later when device support is matured, is this
correct?
If so can you please clarify this in the commit log with
a new version of patch?
next prev parent reply other threads:[~2022-02-24 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 9:25 [PATCH] " Robin Zhang
2022-01-25 1:29 ` Zhang, Qi Z
2022-01-25 14:50 ` Ferruh Yigit
2022-02-15 11:15 ` Ferruh Yigit
2022-02-16 7:45 ` [PATCH v2] " Robin Zhang
2022-02-23 2:42 ` Zhang, Qi Z
2022-02-24 11:37 ` Ferruh Yigit [this message]
2022-02-25 2:00 ` [PATCH v3] " Robin Zhang
2022-02-25 14:07 ` Ferruh Yigit
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=4378bf32-d37b-de67-8ec5-ff9cd5080d2b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=robinx.zhang@intel.com \
--cc=stevex.yang@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).