[LTP] [PATCH 1/2] doc: Remove [Description] title

[Andrea Cervesato]

Hi,

Reviewed-by: Andrea Cervesato <andrea.cervesato@suse.com>

On 2/17/25 13:59, Ricardo B. Marlière wrote:
> As a follow up of commit a3e27df34d6c ("doc: Remove [Description] title"),
> remove some left overs which were not detected with the original RegEx.
>
> Signed-off-by: Ricardo B. Marlière <ricardo@marliere.net>
> ---
>   testcases/kernel/mem/hugetlb/hugemmap/hugemmap17.c | 2 --
>   testcases/kernel/mem/hugetlb/hugemmap/hugemmap19.c | 2 --
>   testcases/kernel/syscalls/fork/fork01.c            | 2 --
>   testcases/kernel/syscalls/fork/fork03.c            | 2 --
>   testcases/kernel/syscalls/fork/fork04.c            | 2 --
>   testcases/kernel/syscalls/fork/fork_procs.c        | 2 --
>   testcases/kernel/syscalls/geteuid/geteuid01.c      | 2 --
>   testcases/kernel/syscalls/geteuid/geteuid02.c      | 2 --
>   8 files changed, 16 deletions(-)
>
> diff --git a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap17.c b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap17.c
> index cca0291ad9d8f3dba3a791ef404088bd2274e1a4..b784005af0309f2728a006ec045cf52d59277dfc 100644
> --- a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap17.c
> +++ b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap17.c
> @@ -5,8 +5,6 @@
>    */
>   
>   /*\
> - * [Descriptiom]
> - *
>    * At one stage, a misconversion of hugetlb_vmtruncate_list to a prio_tree
>    * meant that on 32-bit machines, certain combinations of mapping and
>    * truncations could truncate incorrect pages, or overwrite pmds from
> diff --git a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap19.c b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap19.c
> index c0e41dfa312893264944b62852afc9fd7768202d..13c3c7ac63df5a138cfd6087875dafd6dc924978 100644
> --- a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap19.c
> +++ b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap19.c
> @@ -6,8 +6,6 @@
>    */
>   
>   /*\
> - * [Descripiton]
> - *
>    * At one stage, a misconversion of hugetlb_vmtruncate_list to a
>    * prio_tree meant that on 32-bit machines, truncates at or above 4GB
>    * could truncate lower pages, resulting in BUG_ON()s.
> diff --git a/testcases/kernel/syscalls/fork/fork01.c b/testcases/kernel/syscalls/fork/fork01.c
> index 31ec5d4c1f956cd8f19954ccdb6a893c664ef2d1..d6f6bcfb7bc5ab024bcc03d24c51c958c587ca1d 100644
> --- a/testcases/kernel/syscalls/fork/fork01.c
> +++ b/testcases/kernel/syscalls/fork/fork01.c
> @@ -6,8 +6,6 @@
>    */
>   
>   /*\
> - *[Description]
> - *
>    * - fork returns without error
>    * - fork returns the pid of the child
>    */
> diff --git a/testcases/kernel/syscalls/fork/fork03.c b/testcases/kernel/syscalls/fork/fork03.c
> index c6381dd6737653b025d656e4b4255d27007ea6be..dabe0d498f633e9a8326d104873f7d80c809f016 100644
> --- a/testcases/kernel/syscalls/fork/fork03.c
> +++ b/testcases/kernel/syscalls/fork/fork03.c
> @@ -6,8 +6,6 @@
>    */
>   
>   /*\
> - *[Description]
> - *
>    * Check that child process can use a large text space and do a large number
>    * of operations. In this situation, check for pid == 0 in child and check
>    * for pid > 0 in parent after wait.
> diff --git a/testcases/kernel/syscalls/fork/fork04.c b/testcases/kernel/syscalls/fork/fork04.c
> index 413cd5eb45c5298cd7a58e0300c5f5155f0f6886..ecbbc47fb171017caa641c478e188b66afe89c04 100644
> --- a/testcases/kernel/syscalls/fork/fork04.c
> +++ b/testcases/kernel/syscalls/fork/fork04.c
> @@ -6,8 +6,6 @@
>    */
>   
>   /*\
> - *[Description]
> - *
>    * This test verifies that parent process shares environ variables with the
>    * child and that child doesn't change parent's environ variables.
>    */
> diff --git a/testcases/kernel/syscalls/fork/fork_procs.c b/testcases/kernel/syscalls/fork/fork_procs.c
> index c35bb480ce9e9dcbcda561505e2138c3e477f10e..9e084ed6c0d9b46aaabeec0f0f6ea222596f4468 100644
> --- a/testcases/kernel/syscalls/fork/fork_procs.c
> +++ b/testcases/kernel/syscalls/fork/fork_procs.c
> @@ -4,8 +4,6 @@
>    */
>   
>   /*\
> - *[Description]
> - *
>    * This test spawns multiple processes using fork() and it checks if wait()
>    * returns the right PID once they end up.
>    */
> diff --git a/testcases/kernel/syscalls/geteuid/geteuid01.c b/testcases/kernel/syscalls/geteuid/geteuid01.c
> index 66fb8936c27579670df21b44346f880544e9ffad..1fe38f6c6ffd4954d0ef2cd67364e0342cdd5c52 100644
> --- a/testcases/kernel/syscalls/geteuid/geteuid01.c
> +++ b/testcases/kernel/syscalls/geteuid/geteuid01.c
> @@ -8,8 +8,6 @@
>    */
>   
>   /*\
> - *[Description]
> - *
>    * Check the basic functionality of the geteuid() system call.
>    */
>   
> diff --git a/testcases/kernel/syscalls/geteuid/geteuid02.c b/testcases/kernel/syscalls/geteuid/geteuid02.c
> index eb2272bff34023caa56a2a53e3a3818443642d84..09cb816f446723790893fac108f041d82e2516a0 100644
> --- a/testcases/kernel/syscalls/geteuid/geteuid02.c
> +++ b/testcases/kernel/syscalls/geteuid/geteuid02.c
> @@ -6,8 +6,6 @@
>    */
>   
>   /*\
> - *[Description]
> - *
>    * Check that geteuid() return value matches value from /proc/self/status.
>    */
>   
>