Re: [PATCH v6 02/21] libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support

From: Dan Williams
Date: Wed Jun 17 2015 - 17:35:31 EST

On Wed, Jun 17, 2015 at 2:59 PM, Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote:
> On Thursday, June 11, 2015 04:10:18 PM Dan Williams wrote:
>> A struct nvdimm_bus is the anchor device for registering nvdimm
>> resources and interfaces, for example, a character control device,
>> nvdimm devices, and I/O region devices. The ACPI NFIT (NVDIMM Firmware
>> Interface Table) is one possible platform description for such
>> non-volatile memory resources in a system. The nfit.ko driver attaches
>> to the "ACPI0012" device that indicates the presence of the NFIT and
>> parses the table to register a struct nvdimm_bus instance.
>> Cc: <linux-acpi@xxxxxxxxxxxxxxx>
>> Cc: Lv Zheng <lv.zheng@xxxxxxxxx>
>> Cc: Robert Moore <robert.moore@xxxxxxxxx>
>> Cc: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
>> Acked-by: Jeff Moyer <jmoyer@xxxxxxxxxx>
>> Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>

Thanks Rafael!

> [cut]
>> +
>> +static struct acpi_driver acpi_nfit_driver = {
>> + .name = KBUILD_MODNAME,
>> + .ids = acpi_nfit_ids,
> But this flag is not needed for now IMO.

Indeed, I'll fold the removal in to a v7 when I add the acks and a few
other straggling bug fixes.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at