mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: barebox@lists.infradead.org
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: [PATCH 4/6] drivers: pwm: imx: Remove redundant assignment
Date: Wed, 29 Jun 2022 09:30:22 +0300	[thread overview]
Message-ID: <20220629063024.3945-4-eagle.alexander923@gmail.com> (raw)
In-Reply-To: <20220629063024.3945-1-eagle.alexander923@gmail.com>

Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
---
 drivers/pwm/pwm-imx.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/drivers/pwm/pwm-imx.c b/drivers/pwm/pwm-imx.c
index 609765d895..c542b72796 100644
--- a/drivers/pwm/pwm-imx.c
+++ b/drivers/pwm/pwm-imx.c
@@ -206,7 +206,7 @@ static int imx_pwm_probe(struct device_d *dev)
 	struct resource *iores;
 	const struct imx_pwm_data *data;
 	struct imx_chip *imx;
-	int ret = 0;
+	int ret;
 
 	ret = dev_get_drvdata(dev, (const void **)&data);
 	if (ret)
@@ -236,11 +236,7 @@ static int imx_pwm_probe(struct device_d *dev)
 	imx->config = data->config;
 	imx->set_enable = data->set_enable;
 
-	ret = pwmchip_add(&imx->chip, dev);
-	if (ret < 0)
-		return ret;
-
-	return 0;
+	return pwmchip_add(&imx->chip, dev);;
 }
 
 static struct driver_d imx_pwm_driver = {
-- 
2.32.0




  parent reply	other threads:[~2022-06-29  6:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  6:30 [PATCH 1/6] drivers: rtc: pcf8536: Remove redundant variable Alexander Shiyan
2022-06-29  6:30 ` [PATCH 2/6] drivers: rtc: abracon: " Alexander Shiyan
2022-06-29  6:30 ` [PATCH 3/6] drivers: regulator: fixed: Fix error path in probe Alexander Shiyan
2022-06-29  6:30 ` Alexander Shiyan [this message]
2022-06-29  6:30 ` [PATCH 5/6] drivers: gpio: pcf857x: Remove redundant assignment Alexander Shiyan
2022-06-29  6:30 ` [PATCH 6/6] drivers: led: pca955x: " Alexander Shiyan
2022-06-29  7:33 ` [PATCH 1/6] drivers: rtc: pcf8536: Remove redundant variable Sascha Hauer

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=20220629063024.3945-4-eagle.alexander923@gmail.com \
    --to=eagle.alexander923@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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