From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v1 06/10] ACPI / scan: Add acpi_dev_get_next_child()
Date: Thu, 02 Jul 2015 01:39:52 +0200 [thread overview]
Message-ID: <1516448.2XgHR7bxIM@vostro.rjw.lan> (raw)
In-Reply-To: <1435676108-20590-7-git-send-email-tomeu.vizoso@collabora.com>
On Tuesday, June 30, 2015 04:55:04 PM Tomeu Vizoso wrote:
> So fwnode_get_next_child_node() can be implemented for ACPI firmware
> nodes.
>
> This re-implements acpi_get_next_child() in terms of
> acpi_dev_get_next_child().
>
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Looks good to me.
> ---
>
> drivers/acpi/scan.c | 5 ++---
> include/linux/acpi.h | 17 +++++++++++++++--
> 2 files changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
> index 2649a06..45cf1b7 100644
> --- a/drivers/acpi/scan.c
> +++ b/drivers/acpi/scan.c
> @@ -1482,10 +1482,9 @@ int acpi_device_add(struct acpi_device *device,
> return result;
> }
>
> -struct acpi_device *acpi_get_next_child(struct device *dev,
> - struct acpi_device *child)
> +struct acpi_device *acpi_dev_get_next_child(struct acpi_device *adev,
> + struct acpi_device *child)
> {
> - struct acpi_device *adev = ACPI_COMPANION(dev);
> struct list_head *head, *next;
>
> if (!adev)
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index fc84e42..2afcdb9 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -752,8 +752,14 @@ int acpi_dev_prop_read_single(struct acpi_device *adev, const char *propname,
> int acpi_dev_prop_read(struct acpi_device *adev, const char *propname,
> enum dev_prop_type proptype, void *val, size_t nval);
>
> -struct acpi_device *acpi_get_next_child(struct device *dev,
> - struct acpi_device *child);
> +struct acpi_device *acpi_dev_get_next_child(struct acpi_device *adev,
> + struct acpi_device *child);
> +
> +static inline struct acpi_device *acpi_get_next_child(struct device *dev,
> + struct acpi_device *child)
> +{
> + return acpi_dev_get_next_child(ACPI_COMPANION(dev), child);
> +}
> #else
> static inline int acpi_dev_get_property(struct acpi_device *adev,
> const char *name, acpi_object_type type,
> @@ -804,6 +810,13 @@ static inline struct acpi_device *acpi_get_next_child(struct device *dev,
> return NULL;
> }
>
> +static inline struct acpi_device *acpi_dev_get_next_child(
> + struct acpi_device *adev,
> + struct acpi_device *child)
> +{
> + return NULL;
> +}
> +
> static inline struct acpi_device *acpi_get_parent_dev(struct acpi_device *adev)
> {
> return NULL;
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2015-07-01 23:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:54 [PATCH v1 0/10] Fixes and API additions for firmware nodes Tomeu Vizoso
2015-06-30 14:54 ` [PATCH v1 01/10] of/platform: Set fwnode field for new devices Tomeu Vizoso
2015-06-30 18:24 ` Grant Likely
2015-07-01 23:32 ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 02/10] i2c: core: Have clients point to their firmware nodes Tomeu Vizoso
2015-07-31 10:36 ` Wolfram Sang
2015-08-06 14:17 ` Tomeu Vizoso
2015-08-06 21:06 ` Wolfram Sang
2015-06-30 14:55 ` [PATCH v1 03/10] mfd: Have child devices " Tomeu Vizoso
2015-06-30 18:24 ` Grant Likely
2015-07-01 7:36 ` Lee Jones
2015-07-01 23:33 ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 04/10] device property: add fwnode_get_parent() Tomeu Vizoso
2015-07-01 23:38 ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 05/10] device property: add fwnode_get_name() Tomeu Vizoso
2015-06-30 18:26 ` Grant Likely
2015-07-01 23:38 ` Rafael J. Wysocki
2015-07-22 11:53 ` Tomeu Vizoso
2015-06-30 14:55 ` [PATCH v1 06/10] ACPI / scan: Add acpi_dev_get_next_child() Tomeu Vizoso
2015-07-01 23:39 ` Rafael J. Wysocki [this message]
2015-06-30 14:55 ` [PATCH v1 07/10] device property: Add fwnode_get_next_child_node() Tomeu Vizoso
2015-07-01 23:40 ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 08/10] device property: add fwnode_is_compatible() Tomeu Vizoso
2015-06-30 18:28 ` Grant Likely
2015-07-01 23:44 ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 09/10] device: property: add fwnode_driver_match_device() Tomeu Vizoso
2015-06-30 18:32 ` Grant Likely
2015-07-01 23:45 ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 10/10] core: platform: use fwnode_driver_match_device() Tomeu Vizoso
2015-07-01 23:46 ` Rafael J. Wysocki
2015-07-10 12:53 ` Tomeu Vizoso
2015-07-11 2:47 ` Rafael J. Wysocki
2015-07-13 6:55 ` Tomeu Vizoso
2015-06-30 15:32 ` [PATCH v1 0/10] Fixes and API additions for firmware nodes Rafael J. Wysocki
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=1516448.2XgHR7bxIM@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=broonie@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomeu.vizoso@collabora.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
all inboxes | Powered by JetHome®