builtin/fsck.c: don't conflate "int" and "enum" in callback
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>
Tue, 1 Jun 2021 00:05:59 +0000 (02:05 +0200)
committerJunio C Hamano <gitster@pobox.com>
Tue, 1 Jun 2021 20:59:15 +0000 (05:59 +0900)
commit28abf260a52b2fb79342d5010e921602e078149f
tree57ae16f5343f320cf333790e9bab50f873a731ff
parent3745e2693de3dd5420221782ed050cae6ebf6fec
builtin/fsck.c: don't conflate "int" and "enum" in callback

Fix a warning on AIX's xlc compiler that's been emitted since my
a1aad71601a (fsck.h: use "enum object_type" instead of "int",
2021-03-28):

    "builtin/fsck.c", line 805.32: 1506-068 (W) Operation between
    types "int(*)(struct object*,enum object_type,void*,struct
    fsck_options*)" and "int(*)(struct object*,int,void*,struct
    fsck_options*)" is not allowed.

I.e. it complains about us assigning a function with a prototype "int"
where we're expecting "enum object_type".

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/fsck.c