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@xxxxxxxxxxxxxxx> > > Reviewed-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> > > Acked-by: Thierry Reding <treding@xxxxxxxxxx> > > Acked-by: Lee Jones <lee.jones@xxxxxxxxxx> > > Signed-off-by: Heikki Krogerus <heikki.krogerus@xxxxxxxxxxxxxxx> > > --- > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
