linux-kernel - Re: [PATCH v2] 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YheJ6OuXOvmQmUGl@orome>
Date:   Thu, 24 Feb 2022 14:36:40 +0100
From:   Thierry Reding <thierry.reding@...il.com>
To:     zhaoxiao <zhaoxiao@...ontech.com>
Cc:     lee.jones@...aro.org, u.kleine-koenig@...gutronix.de,
        linux-arm-kernel@...ts.infradead.org, linux-pwm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] pwm: vt8500: Rename variable pointing to driver
 private data

On Fri, Feb 11, 2022 at 10:37:41AM +0800, zhaoxiao wrote:
> Status quo is that variables of type struct vt8500_chip * are named
> "vt8500", "chip". Because usually only struct pwm_device * variables
> are named "pwm" and "chip" is usually used for variabled of type
> struct pwm_chip *.
> 
> So consistently use the same and non-conflicting name "vt8500".
> 
> Signed-off-by: zhaoxiao <zhaoxiao@...ontech.com>
> ---
>  v2: Rename the "chip" to "vt8500" for variable of type struct vt8500_chip *.
>  drivers/pwm/pwm-vt8500.c | 38 +++++++++++++++++++-------------------
>  1 file changed, 19 insertions(+), 19 deletions(-)

Applied, thanks.

Thierry

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)