linux-kernel - Re: [PATCH] pwm: vt8500: Rename variable pointing to driver private data

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

Message-ID: <YgYT1YQyE9xRvW7I@google.com>
Date:   Fri, 11 Feb 2022 07:44:21 +0000
From:   Lee Jones <lee.jones@...aro.org>
To:     赵晓 <zhaoxiao@...ontech.com>
Cc:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        "thierry.reding" <thierry.reding@...il.com>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-pwm <linux-pwm@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pwm: vt8500: Rename variable pointing to driver private
 data

On Fri, 11 Feb 2022, 赵晓 wrote:

> Thanks for you suggestion. I modified the patch following your instructions and commit the v2 version.&nbsp;
> &nbsp;

Would you be kind enough to turn HTML off in your browser please.

Also, please refrain from top-posting.

Replies should be inline (like this).

> ------------------&nbsp;Original&nbsp;------------------
> From: &nbsp;"Uwe&nbsp;Kleine-König"<u.kleine-koenig@...gutronix.de&gt;;
> Date: &nbsp;Thu, Feb 10, 2022 03:40 PM
> To: &nbsp;"zhaoxiao"<zhaoxiao@...ontech.com&gt;; 
> Cc: &nbsp;"thierry.reding"<thierry.reding@...il.com&gt;; "lee.jones"<lee.jones@...aro.org&gt;; "linux-arm-kernel"<linux-arm-kernel@...ts.infradead.org&gt;; "linux-pwm"<linux-pwm@...r.kernel.org&gt;; "linux-kernel"<linux-kernel@...r.kernel.org&gt;; 
> Subject: &nbsp;Re: [PATCH] pwm: vt8500: Rename variable pointing to driver private data

Please configure your mailer to strip mail headers from the body.

> &nbsp;
> 
> On Wed, Feb 09, 2022 at 02:47:55PM +0800, zhaoxiao wrote:
> &gt; Status quo is that variables of type struct vt8500_chip * are named
> &gt; "pwm", "chip" or "pc". The two formers are all not optimal because
> 
> There are no variables named "pwm" or "pc".
> 
> &gt; usually only struct pwm_device * variables are named "pwm" and "chip" is
> &gt; usually used for variabled of type struct pwm_chip *.
> &gt; 
> &gt; So consistently use the same and non-conflicting name "pc".
> 
> The intention is fine, but you missed a few instances that are named
> "vt8500". The statistic in mainline looks as follows:
> 
> 	$ git grep -o -h -E 'struct vt8500_chip \*[a-zA-Z0-9_]*' linus/master drivers/pwm/pwm-vt8500.c | sort | uniq -c
> 	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2 struct vt8500_chip *chip
> 	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5 struct vt8500_chip *vt8500
> 
> (So there 2 variabled named "chip" (that you renamed to "pc") and 5 that
> are named "vt8500". I prefer to rename the "chip"s to "vt8500".
> 
> Best regards
> Uwe
> 

-- 
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog