Re: [PATCH 03/21] nd_acpi: initial core implementation and nfit skeleton
On Friday, April 17, 2015 09:35:30 PM Dan Williams wrote: > 1/ Autodetect an NFIT table for the ACPI namespace device with _HID of >"ACPI0012" > > 2/ Skeleton implementation to register an NFIT bus. > > The NFIT provided by ACPI is the primary method by which platforms will > discover NVDIMM resources. However, the intent of the > nfit_bus_descriptor abstraction is to contain "provider" specific > details, leaving the nd core to be NFIT-provider agnostic. This > flexibility is exploited in later patches to implement special purpose > providers of test and custom-defined NFITs. > > Cc: > Cc: Robert Moore > Cc: Rafael J. Wysocki > Signed-off-by: Dan Williams So as discussed internally, nfit.h will have to wait for the ACPICA's NFIT support to prevent clashes from happening. Also please CC *all* *patches* with "ACPI" (or "acpi" etc) anywhere in the subject/changelog/body to linux-a...@vger.kernel.org. More comments likely to follow. Thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 03/21] nd_acpi: initial core implementation and nfit skeleton
On Friday, April 17, 2015 09:35:30 PM Dan Williams wrote: 1/ Autodetect an NFIT table for the ACPI namespace device with _HID of ACPI0012 2/ Skeleton implementation to register an NFIT bus. The NFIT provided by ACPI is the primary method by which platforms will discover NVDIMM resources. However, the intent of the nfit_bus_descriptor abstraction is to contain provider specific details, leaving the nd core to be NFIT-provider agnostic. This flexibility is exploited in later patches to implement special purpose providers of test and custom-defined NFITs. Cc: linux-a...@vger.kernel.org Cc: Robert Moore robert.mo...@intel.com Cc: Rafael J. Wysocki rafael.j.wyso...@intel.com Signed-off-by: Dan Williams dan.j.willi...@intel.com So as discussed internally, nfit.h will have to wait for the ACPICA's NFIT support to prevent clashes from happening. Also please CC *all* *patches* with ACPI (or acpi etc) anywhere in the subject/changelog/body to linux-a...@vger.kernel.org. More comments likely to follow. Thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 03/21] nd_acpi: initial core implementation and nfit skeleton
On Fri, 2015-04-17 at 21:35 -0400, Dan Williams wrote: > --- /dev/null > +++ b/drivers/block/nd/Kconfig > + depends on (X86 || IA64 || ARM || ARM64 || SH || XTENSA) I've only skimmed this series. I still noticed this patch contains the only Kconfig typo I know by heart. Because I think you meant to say: depends on (X86 || IA64 || ARM || ARM64 || SUPERH || XTENSA) Is that right? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 03/21] nd_acpi: initial core implementation and nfit skeleton
On Fri, 2015-04-17 at 21:35 -0400, Dan Williams wrote: --- /dev/null +++ b/drivers/block/nd/Kconfig + depends on (X86 || IA64 || ARM || ARM64 || SH || XTENSA) I've only skimmed this series. I still noticed this patch contains the only Kconfig typo I know by heart. Because I think you meant to say: depends on (X86 || IA64 || ARM || ARM64 || SUPERH || XTENSA) Is that right? Paul Bolle -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
