From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dipen Patel <dipenp@nvidia.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
timestamp@lists.linux.dev, linux-tegra@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: [PATCH v1 3/4] hte: tegra194: Remove redundant dev_err()
Date: Tue, 10 Oct 2023 18:17:08 +0300 [thread overview]
Message-ID: <20231010151709.4104747-4-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20231010151709.4104747-1-andriy.shevchenko@linux.intel.com>
There is no need to call the dev_err() function directly to print a custom
message when handling an error from platform_get_irq() function as it is
going to display an appropriate error message in case of a failure.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/hte/hte-tegra194.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/hte/hte-tegra194.c b/drivers/hte/hte-tegra194.c
index 339ff5921ec8..30ef1750a9fa 100644
--- a/drivers/hte/hte-tegra194.c
+++ b/drivers/hte/hte-tegra194.c
@@ -731,10 +731,8 @@ static int tegra_hte_probe(struct platform_device *pdev)
return -ENOMEM;
ret = platform_get_irq(pdev, 0);
- if (ret < 0) {
- dev_err_probe(dev, ret, "failed to get irq\n");
+ if (ret < 0)
return ret;
- }
hte_dev->hte_irq = ret;
ret = devm_request_irq(dev, hte_dev->hte_irq, tegra_hte_isr, 0,
dev_name(dev), hte_dev);
--
2.40.0.1.gaa8946217a0b
next prev parent reply other threads:[~2023-10-10 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:17 [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups Andy Shevchenko
2023-10-10 15:17 ` [PATCH v1 1/4] gpiolib: provide gpio_device_find_by_fwnode() Andy Shevchenko
2023-10-13 9:21 ` Linus Walleij
2023-10-10 15:17 ` [PATCH v1 2/4] hte: tegra194: don't access struct gpio_chip Andy Shevchenko
2023-10-10 16:19 ` Dipen Patel
2023-10-10 19:31 ` Dipen Patel
2023-10-11 5:54 ` Andy Shevchenko
2023-10-11 18:05 ` Dipen Patel
2023-10-10 15:17 ` Andy Shevchenko [this message]
2023-10-11 2:19 ` [PATCH v1 3/4] hte: tegra194: Remove redundant dev_err() Dipen Patel
2023-10-10 15:17 ` [PATCH v1 4/4] hte: tegra194: Switch to LATE_SIMPLE_DEV_PM_OPS() Andy Shevchenko
2023-10-10 19:36 ` Dipen Patel
2023-10-11 5:55 ` Andy Shevchenko
2023-10-11 18:06 ` Dipen Patel
2023-10-11 9:33 ` [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups Bartosz Golaszewski
2023-10-11 10:06 ` Andy Shevchenko
2023-10-11 18:04 ` Dipen Patel
2023-10-11 11:43 ` Linus Walleij
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=20231010151709.4104747-4-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dipenp@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=timestamp@lists.linux.dev \
/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).