On 13-04-19, 11:12, Paul Gortmaker wrote: > These two files are implicitly relying on an instance of including > module.h from <linux/acpi.h>. > > Ideally, header files under include/linux shouldn't be adding > includes of other headers, in anticipation of their consumers, > but just the headers needed for the header itself to pass > parsing with CPP. > > The module.h is particularly bad in this sense, as it itself does > include a whole bunch of other headers, due to the complexity of > module support. > > Here, we make those includes explicit, in order to allow a future > removal of module.h from linux/acpi.h without causing build breakage.
Applied, thanks -- ~Vinod
