From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: linux-acpi@vger.kernel.org
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thierry Reding <treding@nvidia.com>,
Lee Jones <lee.jones@linaro.org>, Daniel Mack <daniel@zonque.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] device property: don't bother the drivers with struct property_set
Date: Thu, 21 Apr 2016 02:15:08 +0200 [thread overview]
Message-ID: <9220737.yhvp89BWgp@vostro.rjw.lan> (raw)
In-Reply-To: <1459252343-105426-1-git-send-email-heikki.krogerus@linux.intel.com>
On Tuesday, March 29, 2016 02:52:23 PM Heikki Krogerus wrote:
> Since device_add_property_set() now always takes a copy of
> the property_set, and also since the fwnode type is always
> hard coded to be FWNODE_PDATA, there is no need for the
> drivers to deliver the entire struct property_set. The
> function can just create the instance of it on its own and
> bind the properties from the drivers to it on the spot.
>
> This renames device_add_property_set() to
> device_add_properties(). The function now takes struct
> property_entry as its parameter instead of struct
> property_set.
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
> Acked-by: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
This patch has been applied to linux-pm.git and is available from its
device-properties branch
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
device-properties
as commit f4d05266032346531b9f889e26aa31a0cf2a9822
device property: don't bother the drivers with struct property_set
on top of 9735a22799b9214d17d3c231fe377fc852f042e9
Linux 4.6-rc2
Thanks,
Rafael
prev parent reply other threads:[~2016-04-21 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 11:52 [PATCH v3] device property: don't bother the drivers with struct property_set Heikki Krogerus
2016-04-11 8:20 ` Lee Jones
2016-04-11 9:52 ` Heikki Krogerus
2016-04-11 13:34 ` Rafael J. Wysocki
2016-04-11 14:05 ` Lee Jones
2016-04-11 14:16 ` Rafael J. Wysocki
2016-04-11 16:20 ` Lee Jones
2016-04-11 21:14 ` Rafael J. Wysocki
2016-04-12 7:24 ` Lee Jones
2016-04-13 4:25 ` Rafael J. Wysocki
2016-04-21 0:15 ` Rafael J. Wysocki [this message]
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=9220737.yhvp89BWgp@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@zonque.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=treding@nvidia.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