From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> To: Thierry Reding <thierry.reding@gmail.com>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com> Cc: linux-pwm@vger.kernel.org, linux-riscv@lists.infradead.org, kernel@pengutronix.de Subject: [PATCH 08/10] pwm: sifive: Consistenly name pwm_chip variables "chip" Date: Fri, 14 Jul 2023 22:56:21 +0200 [thread overview] Message-ID: <20230714205623.2496590-9-u.kleine-koenig@pengutronix.de> (raw) In-Reply-To: <20230714205623.2496590-1-u.kleine-koenig@pengutronix.de> Most variables holding a pointer to a pwm_chip are called "chip" which is also the usual name in most other pwm drivers. Rename the single variable that have a different name to be called "chip", too, for consistency. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> --- drivers/pwm/pwm-sifive.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pwm/pwm-sifive.c b/drivers/pwm/pwm-sifive.c index ae49d67ab2b1..25b9b7d9476a 100644 --- a/drivers/pwm/pwm-sifive.c +++ b/drivers/pwm/pwm-sifive.c @@ -51,9 +51,9 @@ struct pwm_sifive_ddata { }; static inline -struct pwm_sifive_ddata *pwm_sifive_chip_to_ddata(struct pwm_chip *c) +struct pwm_sifive_ddata *pwm_sifive_chip_to_ddata(struct pwm_chip *chip) { - return container_of(c, struct pwm_sifive_ddata, chip); + return container_of(chip, struct pwm_sifive_ddata, chip); } static int pwm_sifive_request(struct pwm_chip *chip, struct pwm_device *pwm) -- 2.39.2
WARNING: multiple messages have this Message-ID (diff)
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> To: Thierry Reding <thierry.reding@gmail.com>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com> Cc: linux-pwm@vger.kernel.org, linux-riscv@lists.infradead.org, kernel@pengutronix.de Subject: [PATCH 08/10] pwm: sifive: Consistenly name pwm_chip variables "chip" Date: Fri, 14 Jul 2023 22:56:21 +0200 [thread overview] Message-ID: <20230714205623.2496590-9-u.kleine-koenig@pengutronix.de> (raw) In-Reply-To: <20230714205623.2496590-1-u.kleine-koenig@pengutronix.de> Most variables holding a pointer to a pwm_chip are called "chip" which is also the usual name in most other pwm drivers. Rename the single variable that have a different name to be called "chip", too, for consistency. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> --- drivers/pwm/pwm-sifive.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pwm/pwm-sifive.c b/drivers/pwm/pwm-sifive.c index ae49d67ab2b1..25b9b7d9476a 100644 --- a/drivers/pwm/pwm-sifive.c +++ b/drivers/pwm/pwm-sifive.c @@ -51,9 +51,9 @@ struct pwm_sifive_ddata { }; static inline -struct pwm_sifive_ddata *pwm_sifive_chip_to_ddata(struct pwm_chip *c) +struct pwm_sifive_ddata *pwm_sifive_chip_to_ddata(struct pwm_chip *chip) { - return container_of(c, struct pwm_sifive_ddata, chip); + return container_of(chip, struct pwm_sifive_ddata, chip); } static int pwm_sifive_request(struct pwm_chip *chip, struct pwm_device *pwm) -- 2.39.2 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-14 20:56 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-14 20:56 [PATCH 00/10] pwm: Constistenly name pwm_chip variables "chip" Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König 2023-07-14 20:56 ` [PATCH 01/10] pwm: Use a consistent name for pwm_chip pointers in the core Uwe Kleine-König 2023-07-14 20:56 ` [PATCH 02/10] pwm: atmel-hlcdc: Use consistent variable naming Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König 2023-07-16 13:04 ` claudiu beznea 2023-07-16 13:04 ` claudiu beznea 2023-07-20 6:53 ` Thierry Reding 2023-07-20 6:53 ` Thierry Reding 2023-07-20 7:29 ` Uwe Kleine-König 2023-07-20 7:29 ` Uwe Kleine-König 2023-07-21 17:58 ` Uwe Kleine-König 2023-07-21 17:58 ` Uwe Kleine-König 2023-07-21 18:26 ` Thierry Reding 2023-07-21 18:26 ` Thierry Reding 2023-07-14 20:56 ` [PATCH 03/10] pwm: bcm-kona: Consistenly name pwm_chip variables "chip" Uwe Kleine-König 2023-07-14 20:56 ` [PATCH 04/10] pwm: crc: " Uwe Kleine-König 2023-07-14 20:56 ` [PATCH 05/10] pwm: cros-ec: " Uwe Kleine-König 2023-07-17 3:34 ` Tzung-Bi Shih 2023-07-14 20:56 ` [PATCH 06/10] pwm: lp3943: " Uwe Kleine-König 2023-07-14 20:56 ` [PATCH 07/10] pwm: rockchip: " Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König 2023-07-14 20:56 ` Uwe Kleine-König [this message] 2023-07-14 20:56 ` [PATCH 08/10] pwm: sifive: " Uwe Kleine-König 2023-07-14 20:56 ` [PATCH 09/10] pwm: sl28cpld: " Uwe Kleine-König 2023-07-19 14:17 ` Michael Walle 2023-07-19 14:39 ` Uwe Kleine-König 2023-07-19 14:55 ` Michael Walle 2023-07-14 20:56 ` [PATCH 10/10] staging: greybus: pwm: " Uwe Kleine-König 2023-07-15 15:04 ` Alex Elder 2023-07-20 6:48 ` [PATCH 00/10] pwm: Constistenly " Thierry Reding 2023-07-20 6:48 ` Thierry Reding 2023-07-20 6:48 ` Thierry Reding 2023-07-20 6:48 ` Thierry Reding 2023-07-20 7:10 ` Uwe Kleine-König 2023-07-20 7:10 ` Uwe Kleine-König 2023-07-20 7:10 ` Uwe Kleine-König 2023-07-20 7:10 ` Uwe Kleine-König 2023-07-20 15:03 ` Thierry Reding 2023-07-20 15:03 ` Thierry Reding 2023-07-20 15:03 ` Thierry Reding 2023-07-20 15:03 ` Thierry Reding 2023-07-20 14:41 ` Thierry Reding 2023-07-20 14:41 ` Thierry Reding 2023-07-20 14:41 ` Thierry Reding 2023-07-20 14:41 ` Thierry Reding 2023-09-11 4:31 ` patchwork-bot+chrome-platform 2023-09-11 4:31 ` patchwork-bot+chrome-platform 2023-09-11 4:31 ` patchwork-bot+chrome-platform 2023-09-11 4:31 ` patchwork-bot+chrome-platform 2023-09-11 4:49 ` patchwork-bot+chrome-platform 2023-09-11 4:49 ` patchwork-bot+chrome-platform 2023-09-11 4:49 ` patchwork-bot+chrome-platform 2023-09-11 4:49 ` patchwork-bot+chrome-platform
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=20230714205623.2496590-9-u.kleine-koenig@pengutronix.de \ --to=u.kleine-koenig@pengutronix.de \ --cc=kernel@pengutronix.de \ --cc=linux-pwm@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=thierry.reding@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.