From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Sakari Ailus <sakari.ailus@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,
kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v5 0/6] Move firmware specific code to firmware specific locations
Date: Wed, 31 May 2017 15:23:12 +0300 [thread overview]
Message-ID: <20170531122312.GH2784@lahna.fi.intel.com> (raw)
In-Reply-To: <1496231532-23601-1-git-send-email-sakari.ailus@linux.intel.com>
On Wed, May 31, 2017 at 02:52:06PM +0300, Sakari Ailus wrote:
> Kieran Bingham (1):
> device property: Add fwnode_graph_get_port_parent
>
> Sakari Ailus (5):
> ACPI: Constify argument to acpi_device_is_present()
> device property: Move FW type specific functionality to FW specific
> files
> device property: Move fwnode graph ops to firmware specific locations
> device property: Introduce fwnode_device_is_available()
> device property: Add FW type agnostic fwnode_graph_get_remote_node
>
> drivers/acpi/device_pm.c | 4 +-
> drivers/acpi/internal.h | 2 +-
> drivers/acpi/property.c | 117 ++++++++++++++++
> drivers/acpi/scan.c | 10 +-
> drivers/base/property.c | 347 ++++++++++++++++++++---------------------------
> drivers/of/property.c | 148 ++++++++++++++++++++
> include/linux/acpi.h | 4 +
> include/linux/fwnode.h | 69 ++++++++++
> include/linux/of.h | 2 +
> include/linux/property.h | 5 +
> 10 files changed, 501 insertions(+), 207 deletions(-)
In general looks good to me now. I commented on one patch but other than
that no objections from me.
For the whole series,
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2017-05-31 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 11:52 [PATCH v5 0/6] Move firmware specific code to firmware specific locations Sakari Ailus
2017-05-31 11:52 ` [PATCH v5 1/6] ACPI: Constify argument to acpi_device_is_present() Sakari Ailus
2017-05-31 11:52 ` [PATCH v5 2/6] device property: Move FW type specific functionality to FW specific files Sakari Ailus
[not found] ` <1496231532-23601-3-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-31 12:19 ` Mika Westerberg
[not found] ` <1496231532-23601-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-31 11:52 ` [PATCH v5 3/6] device property: Move fwnode graph ops to firmware specific locations Sakari Ailus
2017-05-31 11:52 ` [PATCH v5 4/6] device property: Introduce fwnode_device_is_available() Sakari Ailus
2017-05-31 11:52 ` [PATCH v5 5/6] device property: Add FW type agnostic fwnode_graph_get_remote_node Sakari Ailus
2017-05-31 11:52 ` [PATCH v5 6/6] device property: Add fwnode_graph_get_port_parent Sakari Ailus
2017-05-31 12:23 ` Mika Westerberg [this message]
2017-05-31 12:27 ` [PATCH v5 0/6] Move firmware specific code to firmware specific locations Sakari Ailus
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=20170531122312.GH2784@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox