From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Steve Yang <stevex.yang@intel.com>, <dev@dpdk.org>
Cc: <Yuying.Zhang@intel.com>, <aman.deep.singh@intel.com>,
<qiming.yang@intel.com>, <qi.z.zhang@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: Re: [PATCH 1/2] net/ice: add module EEPROM ops for ice
Date: Tue, 25 Jan 2022 14:49:00 +0000 [thread overview]
Message-ID: <31531e36-81c2-e6de-62ae-35f0d89c381c@intel.com> (raw)
In-Reply-To: <20220120025931.574106-2-stevex.yang@intel.com>
On 1/20/2022 2:59 AM, Steve Yang wrote:
> Add new callbacks for eth_dev_ops of ice to get the information
> and data of plugin module EEPROM.
>
> Signed-off-by: Steve Yang<stevex.yang@intel.com>
> ---
> drivers/net/ice/ice_ethdev.c | 160 +++++++++++++++++++++++++++++++++++
> drivers/net/ice/ice_ethdev.h | 25 ++++++
> 2 files changed, 185 insertions(+)
In the 'doc/guides/nics/features/ice.ini' file, the "Module EEPROM dump"
feature already documented as supported, but it is this patch add that
support.
It looks like documenting "Module EEPROM dump" was mistake [1], intention
was to document "EEPROM dump" feature.
Steve, can you please send another patch to fix it?
[1]
Fixes: d0dd1c8e1997 ("net/ice: support EEPROM information getting")
Thanks,
ferruh
next prev parent reply other threads:[~2022-01-25 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 2:59 [PATCH 0/2] " Steve Yang
2022-01-20 2:59 ` [PATCH 1/2] net/ice: " Steve Yang
2022-01-25 1:15 ` Zhang, Qi Z
2022-01-25 14:49 ` Ferruh Yigit [this message]
2022-01-26 0:53 ` Yang, SteveX
2022-01-20 2:59 ` [PATCH 2/2] app/testpmd: fix stack overflow for EEPROM display Steve Yang
2022-02-02 10:00 ` Singh, Aman Deep
2022-02-03 13:15 ` 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=31531e36-81c2-e6de-62ae-35f0d89c381c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Yuying.Zhang@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stevex.yang@intel.com \
--cc=wenzhuo.lu@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).