linux-kernel - Re: [PATCH v1] clang-format: Update and extend the for

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]

Message-ID: <acdf5af3-f256-8d53-ec44-fcef4022ec62@digikod.net>
Date:   Tue, 12 Apr 2022 19:05:49 +0200
From:   Mickaël Salaün <mic@...ikod.net>
To:     Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Kees Cook <keescook@...omium.org>
Cc:     Miguel Ojeda <ojeda@...nel.org>,
        Nathan Chancellor <nathan@...nel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Tom Rix <trix@...hat.com>, bpf <bpf@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        llvm@...ts.linux.dev,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>
Subject: Re: [PATCH v1] clang-format: Update and extend the for_each list with
 tools/

I'm wondering about the ASSERT_* and EXPECT_* macros from 
tools/testing/selftests/kselftest_harness.h
Do you think we should treat them as "for macros" as well? They can 
either be used with or without a following code block.


On 12/04/2022 17:58, Miguel Ojeda wrote:
> Hi Mickaël,
> 
> On Tue, Apr 12, 2022 at 5:39 PM Mickaël Salaün <mic@...ikod.net> wrote:
>>
>> Add tools/ to the shell fragment generating the for_each list and update
>> it.  This is useful to format files in the tools directory (e.g.
>> selftests) with the same coding style as the kernel.
> 
> Sounds good to me. There have been discussions about doing it for the
> entire tree too, so we can start with this.
> 
> Cheers,
> Miguel