From: "Verma, Vishal L" <vishal.l.verma-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Williams,
Dan J" <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
<ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"oceanhehy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<oceanhehy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Jiang,
Dave" <dave.jiang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org"
<rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>
Cc: "linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"hehy1-6jq1YtArVR3QT0dZR+AlfA@public.gmane.org"
<hehy1-6jq1YtArVR3QT0dZR+AlfA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] ACPI: nfit: check dcr immediately following its assignment codes
Date: Wed, 8 Aug 2018 17:42:49 +0000 [thread overview]
Message-ID: <1533750167.7673.0.camel@intel.com> (raw)
In-Reply-To: <1533739821-9864-1-git-send-email-oceanhehy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Wed, 2018-08-08 at 10:50 -0400, Ocean He wrote:
> From: Ocean He <hehy1-6jq1YtArVR3QT0dZR+AlfA@public.gmane.org>
>
> In commit 6697b2cf69d43632 ("nfit: fix multi-interface dimm handling,
> acpi6.1 compatibility"), the check codes of dcr were just following its
> assignment codes. But they were separated by commit ad9ac5e1957531a8
> ("nfit: always associate flush hints").
>
> Just change the check codes back to original position, without function
> change.
>
> Signed-off-by: Ocean He <hehy1-6jq1YtArVR3QT0dZR+AlfA@public.gmane.org>
> ---
> drivers/acpi/nfit/core.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
This seems like unnecessary churn. Does it cause any problems in
practice?
>
> diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
> index 7c47900..c9e4c9a 100644
> --- a/drivers/acpi/nfit/core.c
> +++ b/drivers/acpi/nfit/core.c
> @@ -1078,6 +1078,12 @@ static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> break;
> }
>
> + if (dcr && !nfit_mem->dcr) {
> + dev_err(acpi_desc->dev, "SPA %d missing DCR %d\n",
> + spa->range_index, dcr);
> + return -ENODEV;
> + }
> +
> list_for_each_entry(nfit_flush, &acpi_desc->flushes, list) {
> struct acpi_nfit_flush_address *flush;
> u16 i;
> @@ -1101,12 +1107,6 @@ static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> break;
> }
>
> - if (dcr && !nfit_mem->dcr) {
> - dev_err(acpi_desc->dev, "SPA %d missing DCR %d\n",
> - spa->range_index, dcr);
> - return -ENODEV;
> - }
> -
> if (type == NFIT_SPA_DCR) {
> struct nfit_idt *nfit_idt;
> u16 idt_idx;
WARNING: multiple messages have this Message-ID (diff)
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"oceanhehy@gmail.com" <oceanhehy@gmail.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"hehy1@lenovo.com" <hehy1@lenovo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] ACPI: nfit: check dcr immediately following its assignment codes
Date: Wed, 8 Aug 2018 17:42:49 +0000 [thread overview]
Message-ID: <1533750167.7673.0.camel@intel.com> (raw)
In-Reply-To: <1533739821-9864-1-git-send-email-oceanhehy@gmail.com>
On Wed, 2018-08-08 at 10:50 -0400, Ocean He wrote:
> From: Ocean He <hehy1@lenovo.com>
>
> In commit 6697b2cf69d43632 ("nfit: fix multi-interface dimm handling,
> acpi6.1 compatibility"), the check codes of dcr were just following its
> assignment codes. But they were separated by commit ad9ac5e1957531a8
> ("nfit: always associate flush hints").
>
> Just change the check codes back to original position, without function
> change.
>
> Signed-off-by: Ocean He <hehy1@lenovo.com>
> ---
> drivers/acpi/nfit/core.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
This seems like unnecessary churn. Does it cause any problems in
practice?
>
> diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
> index 7c47900..c9e4c9a 100644
> --- a/drivers/acpi/nfit/core.c
> +++ b/drivers/acpi/nfit/core.c
> @@ -1078,6 +1078,12 @@ static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> break;
> }
>
> + if (dcr && !nfit_mem->dcr) {
> + dev_err(acpi_desc->dev, "SPA %d missing DCR %d\n",
> + spa->range_index, dcr);
> + return -ENODEV;
> + }
> +
> list_for_each_entry(nfit_flush, &acpi_desc->flushes, list) {
> struct acpi_nfit_flush_address *flush;
> u16 i;
> @@ -1101,12 +1107,6 @@ static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> break;
> }
>
> - if (dcr && !nfit_mem->dcr) {
> - dev_err(acpi_desc->dev, "SPA %d missing DCR %d\n",
> - spa->range_index, dcr);
> - return -ENODEV;
> - }
> -
> if (type == NFIT_SPA_DCR) {
> struct nfit_idt *nfit_idt;
> u16 idt_idx;
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"oceanhehy@gmail.com" <oceanhehy@gmail.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"hehy1@lenovo.com" <hehy1@lenovo.com>
Subject: Re: [PATCH] ACPI: nfit: check dcr immediately following its assignment codes
Date: Wed, 8 Aug 2018 17:42:49 +0000 [thread overview]
Message-ID: <1533750167.7673.0.camel@intel.com> (raw)
In-Reply-To: <1533739821-9864-1-git-send-email-oceanhehy@gmail.com>
On Wed, 2018-08-08 at 10:50 -0400, Ocean He wrote:
> From: Ocean He <hehy1@lenovo.com>
>
> In commit 6697b2cf69d43632 ("nfit: fix multi-interface dimm handling,
> acpi6.1 compatibility"), the check codes of dcr were just following its
> assignment codes. But they were separated by commit ad9ac5e1957531a8
> ("nfit: always associate flush hints").
>
> Just change the check codes back to original position, without function
> change.
>
> Signed-off-by: Ocean He <hehy1@lenovo.com>
> ---
> drivers/acpi/nfit/core.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
This seems like unnecessary churn. Does it cause any problems in
practice?
>
> diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
> index 7c47900..c9e4c9a 100644
> --- a/drivers/acpi/nfit/core.c
> +++ b/drivers/acpi/nfit/core.c
> @@ -1078,6 +1078,12 @@ static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> break;
> }
>
> + if (dcr && !nfit_mem->dcr) {
> + dev_err(acpi_desc->dev, "SPA %d missing DCR %d\n",
> + spa->range_index, dcr);
> + return -ENODEV;
> + }
> +
> list_for_each_entry(nfit_flush, &acpi_desc->flushes, list) {
> struct acpi_nfit_flush_address *flush;
> u16 i;
> @@ -1101,12 +1107,6 @@ static int __nfit_mem_init(struct acpi_nfit_desc *acpi_desc,
> break;
> }
>
> - if (dcr && !nfit_mem->dcr) {
> - dev_err(acpi_desc->dev, "SPA %d missing DCR %d\n",
> - spa->range_index, dcr);
> - return -ENODEV;
> - }
> -
> if (type == NFIT_SPA_DCR) {
> struct nfit_idt *nfit_idt;
> u16 idt_idx;
next prev parent reply other threads:[~2018-08-08 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 14:50 [PATCH] ACPI: nfit: check dcr immediately following its assignment codes Ocean He
2018-08-08 14:50 ` Ocean He
2018-08-08 14:50 ` Ocean He
[not found] ` <1533739821-9864-1-git-send-email-oceanhehy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-08-08 17:42 ` Verma, Vishal L [this message]
2018-08-08 17:42 ` Verma, Vishal L
2018-08-08 17:42 ` Verma, Vishal L
[not found] ` <1533750167.7673.0.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-08-09 1:35 ` [External] " Ocean HY1 He
2018-08-09 1:35 ` Ocean HY1 He
2018-08-09 1:35 ` Ocean HY1 He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1533750167.7673.0.camel@intel.com \
--to=vishal.l.verma-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dave.jiang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=hehy1-6jq1YtArVR3QT0dZR+AlfA@public.gmane.org \
--cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
--cc=oceanhehy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \
--cc=ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.