From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>, Daniel Mack <daniel@zonque.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thierry Reding <treding@nvidia.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] device property: don't bother the drivers with struct property_set
Date: Mon, 11 Apr 2016 12:52:34 +0300 [thread overview]
Message-ID: <20160411095234.GA26606@kuha.fi.intel.com> (raw)
In-Reply-To: <20160411082027.GF4592@x1>
On Mon, Apr 11, 2016 at 09:20:27AM +0100, Lee Jones wrote:
> On Tue, 29 Mar 2016, 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>
> > ---
> > arch/arm/mach-pxa/raumfeld.c | 12 ++++--------
Daniel, I think we just need your ACK for this one.
Otherwise I think we are covered.
> > arch/arm/mach-tegra/board-paz00.c | 6 +-----
> > drivers/base/platform.c | 19 ++++++++++---------
> > drivers/base/property.c | 34 +++++++++++++++++++++-------------
> > drivers/mfd/intel-lpss-acpi.c | 12 ++----------
> > drivers/mfd/intel-lpss-pci.c | 20 ++++----------------
> > drivers/mfd/intel-lpss.c | 2 +-
> > drivers/mfd/intel-lpss.h | 4 ++--
> > drivers/mfd/mfd-core.c | 4 ++--
> > include/linux/mfd/core.h | 4 ++--
> > include/linux/platform_device.h | 6 +++---
> > include/linux/property.h | 15 +++------------
> > 12 files changed, 55 insertions(+), 83 deletions(-)
>
> What's happening with this patch? I believe we're still missing
> Acks. Once they are collected someone needs to create an immutable
> branch and send out a pull-request.
Rafael, have you had time to take a look at this?
Thanks,
--
heikki
next prev parent reply other threads:[~2016-04-11 9:52 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 [this message]
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
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=20160411095234.GA26606@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@zonque.org \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--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