From: John Kacur <jkacur@redhat.com>
To: RT <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [PATCH 17/17] rt-tests: ptsematest: Fix unused paramter warnings
Date: Fri, 6 Oct 2023 14:40:11 -0400 [thread overview]
Message-ID: <20231006184011.26699-17-jkacur@redhat.com> (raw)
In-Reply-To: <20231006184011.26699-1-jkacur@redhat.com>
Fix unused paramter warnings
Signed-off-by: John Kacur <jkacur@redhat.com>
---
src/ptsematest/ptsematest.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/ptsematest/ptsematest.c b/src/ptsematest/ptsematest.c
index a9d6c69b6449..5a29718d7bfb 100644
--- a/src/ptsematest/ptsematest.c
+++ b/src/ptsematest/ptsematest.c
@@ -321,13 +321,14 @@ static void process_options(int argc, char *argv[])
static int volatile shutdown;
-static void sighand(int sig)
+static void sighand(int sig __attribute__ ((unused)))
{
shutdown = 1;
}
-static void print_stat(FILE *fp, struct params *receiver, struct params *sender,
- int verbose, int quiet)
+static void print_stat(FILE *fp __attribute__ ((unused)),
+ struct params *receiver, struct params *sender,
+ int verbose __attribute__ ((unused)), int quiet)
{
int i;
@@ -359,7 +360,7 @@ static void write_stats(FILE *f, void *data)
{
struct params_stats *ps = data;
struct params *s, *r;
- unsigned int i;
+ int i;
fprintf(f, " \"num_threads\": %d,\n", num_threads);
fprintf(f, " \"thread\": {\n");
--
2.40.1
prev parent reply other threads:[~2023-10-06 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 18:39 [PATCH 01/17] rt-tests: cyclictest: Remove warnings due different signedness in comparison John Kacur
2023-10-06 18:39 ` [PATCH 02/17] rt-tests: cyclictest: Suppress unused parameters warning John Kacur
2023-10-06 18:39 ` [PATCH 03/17] rt-tests: ssdd: " John Kacur
2023-10-06 18:39 ` [PATCH 04/17] rt-tests: queuelat: " John Kacur
2023-10-06 18:39 ` [PATCH 05/17] rt-tests: cyclicdeadline: Suppress unused parameter warning John Kacur
2023-10-06 18:40 ` [PATCH 06/17] rt-tests: svsematest: Suppress unused paramters warning John Kacur
2023-10-06 18:40 ` [PATCH 07/17] rt-tests: pip_stress: Removed unused parameter John Kacur
2023-10-06 18:40 ` [PATCH 08/17] rt-tests: sigwaittest: Fix some warnings John Kacur
2023-10-06 18:40 ` [PATCH 09/17] rt-tests: rt-migrate-test: " John Kacur
2023-10-06 18:40 ` [PATCH 10/17] rt-tests: signaltest Fix unused parameter warning John Kacur
2023-10-06 18:40 ` [PATCH 11/17] rt-tests: cyclicdeadline: Fix comparison of different signedness John Kacur
2023-10-06 18:40 ` [PATCH 12/17] rt-tests: cyclictest: " John Kacur
2023-10-06 18:40 ` [PATCH 13/17] rt-tests: rt-utils: Suppress warnings about fallthrough John Kacur
2023-10-06 18:40 ` [PATCH 14/17] rt-tests: rt-numa: Fix comparison of different signedness John Kacur
2023-10-06 18:40 ` [PATCH 15/17] rt-tests: pi_stress: Fix various warnings John Kacur
2023-10-06 18:40 ` [PATCH 16/17] rt-tests: pmqtest: " John Kacur
2023-10-06 18:40 ` John Kacur [this message]
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=20231006184011.26699-17-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).