From: Richard Palethorpe <rpalethorpe@suse.de>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v10 1/2] Rewrite aio-stress test using LTP API
Date: Thu, 01 Dec 2022 10:29:28 +0000 [thread overview]
Message-ID: <87h6yfifbr.fsf@suse.de> (raw)
In-Reply-To: <20221130135451.28399-2-andrea.cervesato@suse.com>
Hello,
Andrea Cervesato via ltp <ltp@lists.linux.it> writes:
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> }
> }
>
> @@ -1111,7 +1040,7 @@ void global_thread_throughput(struct thread_info *t, char *this_stage)
> * various timings are printed in between the stages, along with
> * thread synchronization if there are more than one threads.
> */
> -int worker(struct thread_info *t)
> +static int *worker(struct thread_info *t)
> {
> struct io_oper *oper;
> char *this_stage = NULL;
> @@ -1126,15 +1055,18 @@ restart:
There is a useless variable below this line reported by clang
aio-stress.c:1049:6: warning: variable 'iteration' set but not used [-Wunused-but-set-variable]
int iteration = 0;
It's incremented, but never read from. This seems to have always been
the case and it should be removed.
With that
Reviewed-by: Richard Palethorpe <rpalethorpe@suse.com>
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-01 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 13:54 [LTP] [PATCH v10 0/2] Rewrite aio-stress test Andrea Cervesato via ltp
2022-11-30 13:54 ` [LTP] [PATCH v10 1/2] Rewrite aio-stress test using LTP API Andrea Cervesato via ltp
2022-12-01 10:29 ` Richard Palethorpe [this message]
2022-12-09 11:29 ` Cyril Hrubis
2022-12-09 12:37 ` Cyril Hrubis
2022-11-30 13:54 ` [LTP] [PATCH v10 2/2] Merge ltp-aio-stress part2 with part1 Andrea Cervesato via ltp
2022-12-01 10:33 ` Richard Palethorpe
2022-12-08 9:46 ` [LTP] [PATCH v10 0/2] Rewrite aio-stress test Richard Palethorpe
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=87h6yfifbr.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.