From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Chen, LingliX" <linglix.chen@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, LingliX" <linglix.chen@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist:add foxville not supoort case
Date: Fri, 18 Jun 2021 07:40:19 +0000 [thread overview]
Message-ID: <6104e7546a4d45ec91f20238121bc457@intel.com> (raw)
In-Reply-To: <20210616121301.5734-1-linglix.chen@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Lingli Chen
> Sent: 2021年6月16日 20:13
> To: dts@dpdk.org
> Cc: Chen, LingliX <linglix.chen@intel.com>
> Subject: [dts] [PATCH V1] conf/test_case_checklist:add foxville not supoort case
>
> According to dpdk commit 312312e928c7 (app/testpmd: fix bitmap of link
> speeds when force speed):
> foxville not supoort:change_linkspeed.
Commit 312312e928c7 (app/testpmd: fix bitmap of link
> speeds when force speed) tells:
app/testpmd: fix bitmap of link speeds when force speed
Currently, when the user sets force link speed through 'link_speeds',
bit(0) of 'link_speeds' is not set to 1(ETH_LINK_SPEED_FIXED),
which conflicts with the definition.
I don't understand how do you get " foxville not supoort:change_linkspeed ", could you please clarify it?
>
> Signed-off-by: Lingli Chen <linglix.chen@intel.com>
> ---
> conf/test_case_checklist.json | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index
> 1a686d8e..8523f61e 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2862,6 +2862,7 @@
> "NIC": [
> "powerville",
> "springville",
> + "foxville",
> "columbiaville_25g",
> "columbiaville_100g"
> ],
> --
> 2.17.1
prev parent reply other threads:[~2021-06-18 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 12:13 Lingli Chen
2021-06-16 3:47 ` Chen, LingliX
2021-06-18 7:40 ` 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=6104e7546a4d45ec91f20238121bc457@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=linglix.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).