From: Thierry Reding <thierry.reding@gmail.com>
To: zhaoxiao <zhaoxiao@uniontech.com>
Cc: lee.jones@linaro.org, u.kleine-koenig@pengutronix.de,
linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pwm: vt8500: Rename variable pointing to driver private data
Date: Thu, 24 Feb 2022 14:36:40 +0100 [thread overview]
Message-ID: <YheJ6OuXOvmQmUGl@orome> (raw)
In-Reply-To: <20220211023741.24061-1-zhaoxiao@uniontech.com>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
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@uniontech.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
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-24 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 2:37 [PATCH v2] pwm: vt8500: Rename variable pointing to driver private data zhaoxiao
2022-02-24 13:36 ` Thierry Reding [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YheJ6OuXOvmQmUGl@orome \
--to=thierry.reding@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zhaoxiao@uniontech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).