xfsdump: Use c99 defined int64_t instead of __int64_t

Signed-off-by Khem Raj <[email protected]>

---
 common/hsmapi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

common/hsmapi.c +1 -1

index 6054773..0709dbe 100644
@@ -585,7 +585,7 @@ HsmModifyExtentMap(
 	struct getbmapx	*bmap)
 {
 	dmf_f_ctxt_t	*dmf_f_ctxtp = (dmf_f_ctxt_t *)contextp;
-	__int64_t	length;
+	int64_t		length;
 
 	if (bmap[0].bmv_entries <= 0) {
 		return 1;	/* caller must already be at EOF */

Seems fine, but are the __uint32_t instances in the code not a problem?

Thanks,
-Eric

Quoted 19 lines · Khem Raj

Signed-off-by Khem Raj <[email protected]>

---
 common/hsmapi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

common/hsmapi.c +1 -1

index 6054773..0709dbe 100644
@@ -585,7 +585,7 @@ HsmModifyExtentMap(
      struct getbmapx *bmap)
 {
      dmf_f_ctxt_t    *dmf_f_ctxtp = (dmf_f_ctxt_t *)contextp;
-     __int64_t       length;
+     int64_t         length;
 
      if (bmap[0].bmv_entries <= 0) {
              return 1;       /* caller must already be at EOF */

Quoted 2 lines · Eric Sandeen

Seems fine, but are the __uint32_t instances in the code not a problem?

yes they are and I had a seprate patch for them, which I will send once I have fixed the tab formatting issues with it. May be I should squash then into one