From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "pvukkisala@marvell.com" <pvukkisala@marvell.com>
Subject: Re: [dts] [PATCH] test_case_checklist.json: retrieve_eeprom is not supported for cavium_a063 and cavium_a064
Date: Fri, 20 Dec 2019 07:58:36 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB8A16D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1576474789-11319-1-git-send-email-nareddy@marvell.com>
Could you please rework it, because code base changed.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Monday, December 16, 2019 1:40 PM
> To: dts@dpdk.org
> Cc: pvukkisala@marvell.com; Praneeth Reddy <nareddy@marvell.com>
> Subject: [dts] [PATCH] test_case_checklist.json: retrieve_eeprom is not
> supported for cavium_a063 and cavium_a064
>
> From: Praneeth Reddy <nareddy@marvell.com>
>
> Added cavium_a063 and cavium_a064 to checklist
>
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
> conf/test_case_checklist.json | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 38b1335..cd23a0b 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2415,5 +2415,21 @@
> "Bug ID": "",
> "Comments": "the nic not support this case: ice_dev_filter_ctrl(): Filter
> type (6) not supported"
> }
> + ],
> + "retrieve_eeprom": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> + "cavium_a063",
> + "cavium_a064"
> + ],
> + "Target": [
> + "ALL"
> + ],
> + "Bug ID": "",
> + "Comments": "the nic not support this case: retrieve_eeprom not
> supported"
> + }
> ]
> }
> --
> 1.8.3.1
prev parent reply other threads:[~2019-12-20 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 5:39 nareddy
2019-12-20 7:58 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BB8A16D@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=nareddy@marvell.com \
--cc=pvukkisala@marvell.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).