netdev - Re: [PATCH] core: Variable type completion

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] [day] [month] [year] [list]

Message-ID: <20220819173430.20f8653b@kernel.org>
Date:   Fri, 19 Aug 2022 17:34:30 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Tejun Heo <tj@...nel.org>, Xin Gao <gaoxin@...rlc.com>
Cc:     davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
        sdf@...gle.com, daniel@...earbox.net, ast@...nel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] core: Variable type completion

On Fri, 19 Aug 2022 14:07:26 -1000 Tejun Heo wrote:
> On Fri, Aug 19, 2022 at 04:47:31PM -0700, Jakub Kicinski wrote:
> > On Wed, 17 Aug 2022 09:35:29 +0800 Xin Gao wrote:  
> > > 'unsigned int' is better than 'unsigned'.  
> > 
> > Please resend with the following subject:
> > 
> > [PATCH net-next] net: cgroup: complete unsigned type name  
> 
> Out of curiosity, why is 'unsigned int' better than 'unsigned'?

Good question, a citation in the commit message would also be good.