linux-kernel - Re: [PATCH 3/3] firmware: xilinx: Properly align function parameter

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: <2f5a0baf-e45b-2687-cff0-922e55fd6930@xilinx.com>
Date:   Wed, 2 Dec 2020 08:38:08 +0100
From:   Michal Simek <michal.simek@...inx.com>
To:     Joe Perches <joe@...ches.com>,
        Michal Simek <michal.simek@...inx.com>,
        <linux-kernel@...r.kernel.org>, <monstr@...str.eu>,
        <git@...inx.com>
CC:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jolly Shah <jolly.shah@...inx.com>,
        Rajan Vaja <rajan.vaja@...inx.com>,
        Tejas Patel <tejas.patel@...inx.com>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 3/3] firmware: xilinx: Properly align function parameter



On 01. 12. 20 20:42, Joe Perches wrote:
> On Tue, 2020-12-01 at 16:50 +0100, Michal Simek wrote:
>> Fix parameters alignment reported by checkpatch --strict.
> 
> Please use a newer checkpatch as the 80 column warning
> isn't enforced quite the same way.

I was using it but saw 80 lines breakage in editor that's why I put it
there.

> 
>> diff --git a/include/linux/firmware/xlnx-zynqmp.h b/include/linux/firmware/xlnx-zynqmp.h
> []
>> @@ -456,7 +456,8 @@ static inline int zynqmp_pm_sd_dll_reset(u32 node_id, u32 type)
>>  }
>>  
>>
>>  static inline int zynqmp_pm_reset_assert(const enum zynqmp_pm_reset reset,
>> -			   const enum zynqmp_pm_reset_action assert_flag)
>> +					 const enum zynqmp_pm_reset_action
>> +					 assert_flag)
> 
> I think these changes aren't very good as it separates
> the type from the variable name.

I have retest it and I can't see any warning when they are on the same
line. Will send v2 with fixing this.

Thanks,
Michal