Re: [PATCH 00/20] Move firmware specific code to firmware specific locations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday, February 23, 2017 07:00:56 PM Sakari Ailus wrote:
> Hi,
> 
> This set moves firmware specific implementations of the device / fwnode
> property API to locations that are specific to firmware implementation,
> still leaving property set (which isn't really firmware) implementation in
> drivers/base/property.c.
> 
> The set begins with a few bugfixes (patches 1--3), followed by adding
> fwnode_operations struct and then gradually moving firmware dependent code
> to drivers/acpi/property.c and drivers/of/base.c.
> 
> The set depends on the ACPI graph support here:
> 
> <URL:http://marc.info/?l=linux-acpi&m=148786716920942&w=2>
> 
> Comments are welcome.

Patches [1-3/20] from this series seem to be fixes that don't depend on the
rest of it and don't depend on the other series you posted.

If that is the case, it would be good to get them in during this cycle instead
of sitting on them for several weeks.

So is that the case?

Thanks,
Rafael

--
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



[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux