From: Stephen Boyd <swboyd@chromium.org>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>, Kamil Debski <kamil@wypas.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] driver core: platform: Introduce platform_get_irq_optional()
Date: Wed, 28 Aug 2019 08:46:48 -0700 [thread overview]
Message-ID: <5d66a1e9.1c69fb81.45c82.ec94@mx.google.com> (raw)
In-Reply-To: <20190828083411.2496-1-thierry.reding@gmail.com>
Quoting Thierry Reding (2019-08-28 01:34:10)
> From: Thierry Reding <treding@nvidia.com>
>
> In some cases the interrupt line of a device is optional. Introduce a
> new platform_get_irq_optional() that works much like platform_get_irq()
> but does not output an error on failure to find the interrupt.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
Thanks!
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
next prev parent reply other threads:[~2019-08-28 15:46 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 ` [PATCH 2/2] hwmon: pwm-fan: Use platform_get_irq_optional() Thierry Reding
2019-08-28 9:10 ` 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 [this message]
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=5d66a1e9.1c69fb81.45c82.ec94@mx.google.com \
--to=swboyd@chromium.org \
--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=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: 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).