From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
sudeep.holla@arm.com, lorenzo.pieralisi@arm.com,
rafael@kernel.org, mark.rutland@arm.com, broonie@kernel.org,
robh@kernel.org, ahs3@redhat.com, frowand.list@gmail.com
Subject: Re: [PATCH v4 4/5] device property: Introduce fwnode_device_is_available()
Date: Wed, 31 May 2017 13:12:35 +0300 [thread overview]
Message-ID: <9a32d562-8335-2b10-8aaa-e74d919636a0@linux.intel.com> (raw)
In-Reply-To: <20170531095804.GD2784@lahna.fi.intel.com>
On 05/31/17 12:58, Mika Westerberg wrote:
> On Mon, May 22, 2017 at 11:53:21AM +0300, Sakari Ailus wrote:
>> /**
>> + * fwnode_device_is_available - check if a device is available for use
>> + * @fwnode: Pointer to the fwnode of the device.
>> + */
>> +bool fwnode_device_is_available(struct fwnode_handle *fwnode)
>
> Can it be const instead? Ditto for of_fwnode_device_is_available() and
> acpi_fwnode_device_is_available) and the .device_available() hook.
>
In principle yes, but it will require other changes in the ACPI
framework as well that do not suit well yet for this patchset.
I have another patchset that makes fwnode arguments const whenever it's
possible:
<URL:http://www.spinics.net/lists/devicetree/msg177564.html>
--
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2017-05-31 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 8:53 [PATCH v4 0/5] Move firmware specific code to firmware specific locations Sakari Ailus
[not found] ` <1495443202-22817-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-22 8:53 ` [PATCH v4 1/5] ACPI: Constify argument to acpi_device_is_present() Sakari Ailus
2017-05-22 8:53 ` [PATCH v4 3/5] device property: Move fwnode graph ops to firmware specific locations Sakari Ailus
2017-05-22 8:53 ` [PATCH v4 2/5] device property: Move FW type specific functionality to FW specific files Sakari Ailus
2017-05-31 9:44 ` Mika Westerberg
2017-05-31 10:08 ` Sakari Ailus
2017-05-22 8:53 ` [PATCH v4 4/5] device property: Introduce fwnode_device_is_available() Sakari Ailus
2017-05-31 9:58 ` Mika Westerberg
2017-05-31 10:12 ` Sakari Ailus [this message]
2017-05-31 10:17 ` Mika Westerberg
2017-05-22 8:53 ` [PATCH v4 5/5] device property: Add FW type agnostic fwnode_graph_get_remote_node Sakari Ailus
[not found] ` <1495443202-22817-6-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-31 10:02 ` Mika Westerberg
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=9a32d562-8335-2b10-8aaa-e74d919636a0@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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 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.