From: Nicholas Piggin <npiggin@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Andrew Jones <andrew.jones@linux.dev>,
kvm@vger.kernel.org, Subhasish Ghosh <subhasish.ghosh@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: [kvm-unit-tests PATCH 2/6] arm: Fix kerneldoc
Date: Fri, 26 Jul 2024 17:04:43 +1000 [thread overview]
Message-ID: <20240726070456.467533-3-npiggin@gmail.com> (raw)
In-Reply-To: <20240726070456.467533-1-npiggin@gmail.com>
Some invalid kerneldoc comments crept in while centos ci job was down.
Cc: Subhasish Ghosh <subhasish.ghosh@arm.com>
Cc: Joey Gouly <joey.gouly@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Fixes: d47d370c8f ("arm: Add test for FPU/SIMD context save/restore")
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
arm/fpu.c | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/arm/fpu.c b/arm/fpu.c
index 39413fc3e..edbd9a946 100644
--- a/arm/fpu.c
+++ b/arm/fpu.c
@@ -212,8 +212,8 @@ static void nr_cpu_check(int nr)
report_abort("At least %d cpus required", nr);
}
-/**
- * @brief check if the FPU/SIMD/SVE register contents are the same as
+/*
+ * check if the FPU/SIMD/SVE register contents are the same as
* the input data provided.
*/
static uint32_t __fpuregs_testall(uint64_t *indata, int sve)
@@ -256,8 +256,8 @@ static uint32_t __fpuregs_testall(uint64_t *indata, int sve)
return result;
}
-/**
- * @brief writes randomly sampled data into the FPU/SIMD registers.
+/*
+ * Write randomly sampled data into the FPU/SIMD registers.
*/
static void __fpuregs_writeall_random(uint64_t **indata, int sve)
{
@@ -315,9 +315,9 @@ static void sveregs_testall_run(void *data)
"SVE register save/restore mask: 0x%x", result);
}
-/**
- * @brief This test uses two CPUs to test FPU/SIMD save/restore
- * @details CPU1 writes random data into FPU/SIMD registers,
+/*
+ * This test uses two CPUs to test FPU/SIMD save/restore
+ * CPU1 writes random data into FPU/SIMD registers,
* CPU0 corrupts/overwrites the data and finally CPU1 checks
* if the data remains unchanged in its context.
*/
@@ -344,9 +344,9 @@ static void fpuregs_context_switch_cpu1(int sve)
free(indata_local);
}
-/**
- * @brief This test uses two CPUs to test FPU/SIMD save/restore
- * @details CPU0 writes random data into FPU/SIMD registers,
+/*
+ * This test uses two CPUs to test FPU/SIMD save/restore
+ * CPU0 writes random data into FPU/SIMD registers,
* CPU1 corrupts/overwrites the data and finally CPU0 checks if
* the data remains unchanged in its context.
*/
@@ -374,7 +374,7 @@ static void fpuregs_context_switch_cpu0(int sve)
free(indata_local);
}
-/**
+/*
* Checks if during context switch, FPU/SIMD registers
* are saved/restored.
*/
@@ -384,7 +384,7 @@ static void fpuregs_context_switch(void)
fpuregs_context_switch_cpu1(0);
}
-/**
+/*
* Checks if during context switch, SVE registers
* are saved/restored.
*/
--
2.45.2
next prev parent reply other threads:[~2024-07-26 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 7:04 [kvm-unit-tests PATCH 0/6] Checking and CI improvements Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 1/6] gitlab-ci: fix CentOS mirror list Nicholas Piggin
2024-07-26 7:04 ` Nicholas Piggin [this message]
2024-07-26 9:40 ` [kvm-unit-tests PATCH 2/6] arm: Fix kerneldoc Suzuki K Poulose
2024-07-26 7:04 ` [kvm-unit-tests PATCH 3/6] gitlab-ci: upgrade to CentOS 8 Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 4/6] gitlab-ci: Move check-kerneldoc test out of the centos test Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 5/6] gitlab-ci: add a shellcheck test Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 6/6] checkpatch support Nicholas Piggin
2024-07-29 13:12 ` [kvm-unit-tests PATCH 0/6] Checking and CI improvements Andrew Jones
2024-08-12 14:32 ` Andrew Jones
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=20240726070456.467533-3-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=andrew.jones@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=subhasish.ghosh@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=thuth@redhat.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