michaelh/zephyr
1
0
Fork 0
Code Releases Activity

tests: unit: util: Fix compliance check warnings

Browse source 
As code is moved from test.inc to main.c a compliance check is
run for the first time on that code. Fixing warnings.

Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
This commit is contained in:
Krzysztof Chruściński 2023-11-21 14:22:02 +01:00 • committed by Fabio Baltieri
commit c0bb064d4e
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
tests/unit/util/main.c
View file

@ -68,7 +68,7 @@ ZTEST(util, test_COND_CODE_1) {
#define TEST_DEFINE_1 1
#define TEST_DEFINE_0 0
/* Test validates that expected code has been injected. Failure would
* be seen in compilation (lack of variable or ununsed variable.
* be seen in compilation (lack of variable or unused variable).
*/
COND_CODE_1(1, (uint32_t x0 = 1;), (uint32_t y0;))
zassert_true((x0 == 1));
@ -85,7 +85,7 @@ ZTEST(util, test_COND_CODE_1) {
ZTEST(util, test_COND_CODE_0) {
/* Test validates that expected code has been injected. Failure would
* be seen in compilation (lack of variable or ununsed variable.
* be seen in compilation (lack of variable or unused variable).
*/
COND_CODE_0(0, (uint32_t x0 = 1;), (uint32_t y0;))
zassert_true((x0 == 1));
@ -173,7 +173,7 @@ static int inc_func(bool cleanup)
{
static int a;
if (cleanup) {
if (cleanup) {
a = 1;
}