From: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
To: <ruifeng.wang@arm.com>, <zhoumin@loongson.cn>,
<drc@linux.vnet.ibm.com>, <kda@semihalf.com>,
<bruce.richardson@intel.com>, <konstantin.v.ananyev@yandex.ru>
Cc: <dev@dpdk.org>
Subject: [PATCH v2 1/2] test/cpuflags: removed test for NUMFLAGS
Date: Thu, 10 Aug 2023 23:07:54 -0700 [thread overview]
Message-ID: <20230811060755.481572-1-sivaprasad.tummala@amd.com> (raw)
In-Reply-To: <20230802211150.939121-1-sivaprasad.tummala@amd.com>
This patch removes RTE_CPUFLAG_NUMFLAGS to allow new CPU
features without breaking ABI each time.
Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
---
app/test/test_cpuflags.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/app/test/test_cpuflags.c b/app/test/test_cpuflags.c
index a0e342ae48..2b8563602c 100644
--- a/app/test/test_cpuflags.c
+++ b/app/test/test_cpuflags.c
@@ -322,15 +322,6 @@ test_cpuflags(void)
CHECK_FOR_FLAG(RTE_CPUFLAG_LBT_MIPS);
#endif
- /*
- * Check if invalid data is handled properly
- */
- printf("\nCheck for invalid flag:\t");
- result = rte_cpu_get_flag_enabled(RTE_CPUFLAG_NUMFLAGS);
- printf("%s\n", cpu_flag_result(result));
- if (result != -ENOENT)
- return -1;
-
return 0;
}
--
2.34.1
next prev parent reply other threads:[~2023-08-11 6:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 21:11 [PATCH 1/2] eal: remove RTE_CPUFLAG_NUMFLAGS Sivaprasad Tummala
2023-08-02 21:11 ` [PATCH 2/2] test/cpuflags: " Sivaprasad Tummala
2023-08-02 23:50 ` [PATCH 1/2] eal: " Stanisław Kardach
2023-08-11 4:02 ` Tummala, Sivaprasad
2023-08-11 6:07 ` Sivaprasad Tummala [this message]
2023-08-11 6:07 ` [PATCH v2 2/2] eal: remove NUMFLAGS enumeration Sivaprasad Tummala
2023-08-15 6:10 ` Stanisław Kardach
2023-09-19 14:47 ` David Marchand
2023-09-20 6:00 ` Stanisław Kardach
2023-09-20 7:34 ` David Marchand
2023-09-21 13:18 ` Tummala, Sivaprasad
2023-09-21 14:49 ` Stanisław Kardach
2023-09-27 11:55 ` Ferruh Yigit
2023-09-27 13:48 ` Stanisław Kardach
2023-09-27 14:09 ` Ferruh Yigit
2023-09-27 15:03 ` Stanisław Kardach
2023-09-27 16:13 ` Ferruh Yigit
2023-09-27 13:13 ` Ferruh Yigit
2023-09-28 9:31 ` Tummala, Sivaprasad
2023-10-06 8:27 ` David Marchand
2023-10-06 11:19 ` 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=20230811060755.481572-1-sivaprasad.tummala@amd.com \
--to=sivaprasad.tummala@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=kda@semihalf.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=ruifeng.wang@arm.com \
--cc=zhoumin@loongson.cn \
/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).