linux-kernel - Re: AW: [PATCH 17/24] get_phys_pages.3: Write 'long' instead of 'long int'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 11 Sep 2020 21:24:08 +0200
From:   Alejandro Colomar <colomar.6.4.3@...il.com>
To:     Walter Harms <wharms@....de>,
        "mtk.manpages@...il.com" <mtk.manpages@...il.com>
Cc:     "linux-man@...r.kernel.org" <linux-man@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: AW: [PATCH 17/24] get_phys_pages.3: Write 'long' instead of 'long
 int'

On 2020-09-11 15:07, Walter Harms wrote:
> 
> 
> sys/sysinfo.h:extern long int get_phys_pages (void)
> 
> for the real world i would say that long int == long but for the same reason
> i would say what the include says and stay away from discussions.
> 
> jm2c,
>   wh

I think that the man-pages don't need to follow other projects' 
inconsistencies.  'long int' == 'long', so I think it's better to be 
consistent here and hope that the other projects do that too.

A newbie may see 'long int' and 'long' used differently in the man-pages 
and wonder that there might be a good reason for that to happen, and 
won't understand why.

So I stand by this patch.

Cheers,

Alex