[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fa493113c74a0618d34f0e5d88e4402abe3e69c.camel@intel.com>
Date: Wed, 18 Nov 2020 20:50:56 +0000
From: "Verma, Vishal L" <vishal.l.verma@...el.com>
To: "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"Jiang, Dave" <dave.jiang@...el.com>,
"lenb@...nel.org" <lenb@...nel.org>,
"thunder.leizhen@...wei.com" <thunder.leizhen@...wei.com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"Weiny, Ira" <ira.weiny@...el.com>
Subject: Re: [PATCH 1/1] ACPI/nfit: correct the badrange to be reported in
nfit_handle_mce()
On Wed, 2020-11-18 at 16:41 +0800, Zhen Lei wrote:
> The badrange to be reported should always cover mce->addr.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@...wei.com>
> ---
> drivers/acpi/nfit/mce.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Ah good find, agreed with Dan that this is stable material.
Minor nit, I'd recommend rewording the subject line to something like:
"acpi/nfit: fix badrange insertion in nfit_handle_mce()"
Otherwise, looks good to me.
Reviewed-by: Vishal Verma <vishal.l.verma@...el.com>
>
> diff --git a/drivers/acpi/nfit/mce.c b/drivers/acpi/nfit/mce.c
> index ee8d9973f60b..053e719c7bea 100644
> --- a/drivers/acpi/nfit/mce.c
> +++ b/drivers/acpi/nfit/mce.c
> @@ -63,7 +63,7 @@ static int nfit_handle_mce(struct notifier_block *nb, unsigned long val,
>
> /* If this fails due to an -ENOMEM, there is little we can do */
> nvdimm_bus_add_badrange(acpi_desc->nvdimm_bus,
> - ALIGN(mce->addr, L1_CACHE_BYTES),
> + ALIGN_DOWN(mce->addr, L1_CACHE_BYTES),
> L1_CACHE_BYTES);
> nvdimm_region_notify(nfit_spa->nd_region,
> NVDIMM_REVALIDATE_POISON);
Powered by blists - more mailing lists