From: Uladzislau Rezki <urezki@gmail.com>
To: cgel.zte@gmail.com
Cc: akpm@linux-foundation.org, urezki@gmail.com,
deng.changcheng@zte.com.cn, linux-kernel@vger.kernel.org,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] lib/test_vmalloc.c: use swap() to make code cleaner
Date: Thu, 28 Oct 2021 14:02:20 +0200 [thread overview]
Message-ID: <20211028120220.GA1907@pc638.lan> (raw)
In-Reply-To: <20211028111443.15744-1-deng.changcheng@zte.com.cn>
On Thu, Oct 28, 2021 at 11:14:43AM +0000, cgel.zte@gmail.com wrote:
> From: Changcheng Deng <deng.changcheng@zte.com.cn>
>
> Use swap() in order to make code cleaner. Issue found by coccinelle.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Changcheng Deng <deng.changcheng@zte.com.cn>
> ---
> lib/test_vmalloc.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/lib/test_vmalloc.c b/lib/test_vmalloc.c
> index e14993bc84d2..cf41fd6df42a 100644
> --- a/lib/test_vmalloc.c
> +++ b/lib/test_vmalloc.c
> @@ -393,7 +393,7 @@ static struct test_driver {
> static void shuffle_array(int *arr, int n)
> {
> unsigned int rnd;
> - int i, j, x;
> + int i, j;
>
> for (i = n - 1; i > 0; i--) {
> get_random_bytes(&rnd, sizeof(rnd));
> @@ -402,9 +402,7 @@ static void shuffle_array(int *arr, int n)
> j = rnd % i;
>
> /* Swap indexes. */
> - x = arr[i];
> - arr[i] = arr[j];
> - arr[j] = x;
> + swap(arr[i], arr[j]);
> }
> }
>
> --
> 2.25.1
Makes sense to me: Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Vlad Rezki
next prev parent reply other threads:[~2021-10-28 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 11:14 [PATCH] lib/test_vmalloc.c: use swap() to make code cleaner cgel.zte
2021-10-28 12:02 ` Uladzislau Rezki [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-04 1:16 davidcomponentone
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=20211028120220.GA1907@pc638.lan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=deng.changcheng@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=zealci@zte.com.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