From: Ocean HY1 He <hehy1@lenovo.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
"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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: RE: [External] Re: [PATCH] ACPI: nfit: check dcr immediately following its assignment codes
Date: Thu, 9 Aug 2018 01:35:53 +0000 [thread overview]
Message-ID: <TYAPR03MB31812802CA589A9018B58E5789250@TYAPR03MB3181.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <1533750167.7673.0.camel@intel.com>
> -----Original Message-----
> From: Verma, Vishal L <vishal.l.verma@intel.com>
> Sent: Thursday, August 09, 2018 1:43 AM
> To: Williams, Dan J <dan.j.williams@intel.com>; ross.zwisler@linux.intel.com;
> oceanhehy@gmail.com; Jiang, Dave <dave.jiang@intel.com>; lenb@kernel.org;
> rjw@rjwysocki.net
> Cc: linux-kernel@vger.kernel.org; linux-nvdimm@lists.01.org; linux-
> acpi@vger.kernel.org; Ocean HY1 He <hehy1@lenovo.com>
> Subject: [External] Re: [PATCH] ACPI: nfit: check dcr immediately following its
> assignment codes
>
>
> 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?
>
The original codes do not cause any problems.
Ocean.
> >
> > 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
prev parent reply other threads:[~2018-08-09 1:36 UTC|newest]
Thread overview: 3+ 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 17:42 ` Verma, Vishal L
2018-08-09 1:35 ` Ocean HY1 He [this message]
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=TYAPR03MB31812802CA589A9018B58E5789250@TYAPR03MB3181.apcprd03.prod.outlook.com \
--to=hehy1@lenovo.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=oceanhehy@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=ross.zwisler@linux.intel.com \
--cc=vishal.l.verma@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).