linux-kernel - Re: [PATCH v5] coding-style: Clarify the expectations around bool

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: <20190120190800.64814cd4@lwn.net>
Date:   Sun, 20 Jan 2019 19:08:00 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Jason Gunthorpe <jgg@...pe.ca>
Cc:     Joe Perches <joe@...ches.com>, Gal Pressman <galpress@...zon.com>,
        Bart Van Assche <bvanassche@....org>,
        Stephen Warren <swarren@...dotorg.org>,
        Tariq Toukan <tariqt@...lanox.com>, xavier.huwei@...wei.com,
        netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
        Doug Ledford <dledford@...hat.com>,
        Stephen Warren <swarren@...dia.com>,
        Christoph Hellwig <hch@....de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] coding-style: Clarify the expectations around bool

On Fri, 18 Jan 2019 15:50:47 -0700
Jason Gunthorpe <jgg@...pe.ca> wrote:

> There has been some confusion since checkpatch started warning about bool
> use in structures, and people have been avoiding using it.
> 
> Many people feel there is still a legitimate place for bool in structures,
> so provide some guidance on bool usage derived from the entire thread that
> spawned the checkpatch warning.
> 
> Link: https://lkml.kernel.org/r/CA+55aFwVZk1OfB9T2v014PTAKFhtVan_Zj2dOjnCy3x6E4UJfA@mail.gmail.com
> Signed-off-by: Joe Perches <joe@...ches.com>
> Acked-by: Joe Perches <joe@...ches.com>
> Reviewed-by: Bart Van Assche <bvanassche@....org>
> Acked-by: Jani Nikula <jani.nikula@...el.com>
> Reviewed-by: Joey Pabalinas <joeypabalinas@...il.com>
> Signed-off-by: Jason Gunthorpe <jgg@...lanox.com>

So this seems ready; I've applied it.  

Thanks,

jon