From: Thierry Reding <thierry.reding@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Kamil Debski <kamil@wypas.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Boyd <swboyd@chromium.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] hwmon: pwm-fan: Use platform_get_irq_optional()
Date: Wed, 28 Aug 2019 10:34:11 +0200 [thread overview]
Message-ID: <20190828083411.2496-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20190828083411.2496-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
The PWM fan interrupt is optional, so we don't want an error message in
the kernel log if it wasn't specified.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
drivers/hwmon/pwm-fan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/pwm-fan.c b/drivers/hwmon/pwm-fan.c
index 54c0ff00d67f..42ffd2e5182d 100644
--- a/drivers/hwmon/pwm-fan.c
+++ b/drivers/hwmon/pwm-fan.c
@@ -304,7 +304,7 @@ static int pwm_fan_probe(struct platform_device *pdev)
platform_set_drvdata(pdev, ctx);
- ctx->irq = platform_get_irq(pdev, 0);
+ ctx->irq = platform_get_irq_optional(pdev, 0);
if (ctx->irq == -EPROBE_DEFER)
return ctx->irq;
--
2.22.0
next prev parent reply other threads:[~2019-08-28 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 8:34 [PATCH 1/2] driver core: platform: Introduce platform_get_irq_optional() Thierry Reding
2019-08-28 8:34 ` Thierry Reding [this message]
2019-08-28 9:10 ` [PATCH 2/2] hwmon: pwm-fan: Use platform_get_irq_optional() Bartlomiej Zolnierkiewicz
2019-08-28 15:05 ` Guenter Roeck
2019-08-28 15:38 ` Greg Kroah-Hartman
2019-08-28 15:47 ` Stephen Boyd
2019-08-28 8:57 ` [PATCH 1/2] driver core: platform: Introduce platform_get_irq_optional() Greg Kroah-Hartman
2019-08-28 9:32 ` Thierry Reding
2019-08-28 15:06 ` Guenter Roeck
2019-08-28 15:46 ` Stephen Boyd
2019-08-29 7:44 ` Thierry Reding
2019-08-29 10:10 ` Greg Kroah-Hartman
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=20190828083411.2496-2-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=kamil@wypas.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rafael@kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).