[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4iKHVa0Ek-EkcsYHP6NUTowqdVY-jBkOjas0XS-Zm1n5g@mail.gmail.com>
Date: Fri, 14 Apr 2017 10:30:00 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
Cc: Linux ACPI <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vishal L Verma <vishal.l.verma@...el.com>
Subject: Re: [PATCH 5/5] acpi, nfit: limit ->flush_probe() to initialization work
On Fri, Apr 14, 2017 at 9:58 AM, Dan Williams <dan.j.williams@...el.com> wrote:
> The nvdimm probe flushing mechanism gives userspace a sync point where
> it knows all asynchronous driver probe sequences have completed.
> However, it need not wait for other asynchronous actions, like
> on-demand address-range-scrub. Track the init work separately from other
> work in the workqueue, and only flush the former.
>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
> ---
> drivers/acpi/nfit/core.c | 13 ++++++++++---
> drivers/acpi/nfit/nfit.h | 1 +
> 2 files changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
> index 06738df477db..17cac9d369e0 100644
> --- a/drivers/acpi/nfit/core.c
> +++ b/drivers/acpi/nfit/core.c
> @@ -738,7 +738,7 @@ static void nfit_mem_init_bdw(struct acpi_nfit_desc *acpi_desc,
> }
> }
>
> -static int nfit_mem_dcr_init(struct acpi_nfit_desc *acpi_desc,
> +static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> struct acpi_nfit_system_address *spa)
> {
> struct nfit_mem *nfit_mem, *found;
> @@ -898,7 +898,7 @@ static int nfit_mem_init(struct acpi_nfit_desc *acpi_desc)
> * BDWs are optional.
> */
> list_for_each_entry(nfit_spa, &acpi_desc->spas, list) {
> - rc = nfit_mem_dcr_init(acpi_desc, nfit_spa->spa);
> + rc = __nfit_mem_init(acpi_desc, nfit_spa->spa);
Whoops, this function rename should have been folded into the previous patch.
Powered by blists - more mailing lists