Re: [PATCH] xfsdump: Use c99 defined int64_t instead of __int64_t

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Sep 9, 2017 at 12:09 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> 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

> Thanks,
> -Eric
>
> On 9/9/17 10:02 AM, Khem Raj wrote:
>> Signed-off-by: Khem Raj <raj.khem@xxxxxxxxx>
>> ---
>>  common/hsmapi.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/common/hsmapi.c b/common/hsmapi.c
>> index 6054773..0709dbe 100644
>> --- a/common/hsmapi.c
>> +++ b/common/hsmapi.c
>> @@ -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 */
>>
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux