From 0b4e9013f1f23f0ee0758b2c6abfc446b1376bb0 Mon Sep 17 00:00:00 2001 From: Jeff King Date: Mon, 3 Jul 2023 02:44:18 -0400 Subject: fsck: mark unused parameters in various fsck callbacks There are a few callback functions which are used with the fsck code, but it's natural that not all callbacks need all parameters. For reporting, even something as obvious as "the oid of the object which had a problem" is not always used, as some callers are only checking a single object in the first place. And for both reporting and walking, things like void data pointers and the fsck_options aren't always necessary. But since each such parameter is used by _some_ callback, we have to keep them in the interface. Mark the unused ones in specific callbacks to avoid triggering -Wunused-parameter. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano --- fsck.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'fsck.c') diff --git a/fsck.c b/fsck.c index 3be86616c5..8852e56f6b 100644 --- a/fsck.c +++ b/fsck.c @@ -1310,9 +1310,9 @@ int fsck_buffer(const struct object_id *oid, enum object_type type, int fsck_error_function(struct fsck_options *o, const struct object_id *oid, - enum object_type object_type, + enum object_type object_type UNUSED, enum fsck_msg_type msg_type, - enum fsck_msg_id msg_id, + enum fsck_msg_id msg_id UNUSED, const char *message) { if (msg_type == FSCK_WARN) { -- cgit v1.2.3