[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1863642.qegEO3HtMW@vostro.rjw.lan>
Date: Wed, 17 Jun 2015 23:59:29 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Dan Williams <dan.j.williams@...el.com>
Cc: linux-nvdimm@...ts.01.org, mingo@...nel.org, sfr@...b.auug.org.au,
rafael@...nel.org, neilb@...e.de, gregkh@...uxfoundation.org,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
linux-kernel@...r.kernel.org,
Robert Moore <robert.moore@...el.com>,
linux-acpi@...r.kernel.org, jmoyer@...hat.com,
Lv Zheng <lv.zheng@...el.com>, linux-api@...r.kernel.org,
akpm@...ux-foundation.org, axboe@...nel.dk, hch@....de
Subject: Re: [PATCH v6 02/21] libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support
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@...r.kernel.org>
> Cc: Lv Zheng <lv.zheng@...el.com>
> Cc: Robert Moore <robert.moore@...el.com>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> Acked-by: Jeff Moyer <jmoyer@...hat.com>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
[cut]
> +
> +static struct acpi_driver acpi_nfit_driver = {
> + .name = KBUILD_MODNAME,
> + .ids = acpi_nfit_ids,
> + .flags = ACPI_DRIVER_ALL_NOTIFY_EVENTS,
But this flag is not needed for now IMO.
> + .ops = {
> + .add = acpi_nfit_add,
> + .remove = acpi_nfit_remove,
> + },
> +};
> +
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists