From: "Zijie Pan" <zijie.pan@6wind.com>
To: "Ferruh Yigit" <ferruh.yigit@intel.com>, dev <dev@dpdk.org>
Cc: "remy.horton" <remy.horton@intel.com>,
"john.mcnamara" <john.mcnamara@intel.com>,
"marko.kovacevic" <marko.kovacevic@intel.com>,
thomas <thomas@monjalon.net>
Subject: Re: [PATCH v3 1/5] ethdev: add access to eeprom
Date: Fri, 20 Apr 2018 17:06:12 +0800 [thread overview]
Message-ID: <tencent_45E66AC8363DA3135842FC93@qq.com> (raw)
Hi Ferruh,
I will mark the new APIs as experimental, and sent out a v4 patchset.
Thanks & Regards,
Zijie
------------------ Original ------------------
From: "Ferruh Yigit"<ferruh.yigit@intel.com>;
Date: Thu, Apr 19, 2018 09:34 PM
To: "Zijie Pan"<zijie.pan@6wind.com>; "dev"<dev@dpdk.org>;
Cc: "remy.horton"<remy.horton@intel.com>; "john.mcnamara"<john.mcnamara@intel.com>; "marko.kovacevic"<marko.kovacevic@intel.com>; "thomas"<thomas@monjalon.net>;
Subject: Re: [dpdk-dev] [PATCH v3 1/5] ethdev: add access to eeprom
On 3/21/2018 11:06 AM, Zijie Pan wrote:
> --- a/lib/librte_ether/rte_ethdev_version.map
> +++ b/lib/librte_ether/rte_ethdev_version.map
> @@ -201,6 +201,8 @@ DPDK_18.02 {
> global:
>
> rte_eth_dev_filter_ctrl;
> + rte_eth_dev_get_module_info;
> + rte_eth_dev_get_module_eeprom;
>
> } DPDK_17.11;
New APIs needs to be experimental at least first release they are introduces,
can you please mark them as experimental?
next reply other threads:[~2018-04-20 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 9:06 Zijie Pan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 9:36 [PATCH v2 0/5] get the information and data of EEPROM Zijie Pan
2018-03-21 11:06 ` [PATCH v3 " Zijie Pan
2018-03-21 11:06 ` [PATCH v3 1/5] ethdev: add access to eeprom Zijie Pan
2018-04-19 13:34 ` Ferruh Yigit
2018-04-22 21:13 ` Thomas Monjalon
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=tencent_45E66AC8363DA3135842FC93@qq.com \
--to=zijie.pan@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=remy.horton@intel.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.