From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linda.knippers@hpe.com" <linda.knippers@hpe.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: acpi_nfit_find_poison() question
Date: Wed, 2 Mar 2016 01:47:20 +0000 [thread overview]
Message-ID: <1456883236.4525.12.camel@intel.com> (raw)
In-Reply-To: <56BE64E1.1080500@hpe.com>
On Fri, 2016-02-12 at 18:04 -0500, Linda Knippers wrote:
> Hi Vishal,
>
> I was looking at acpi_nfit_find_poison() and if I'm reading this
> right, I think it's throwing away some ARS results and re-running
> an ARS unnecessarily. More comments below...
Hi Linda,
Sorry for the delay - I was on vacation and took a while to catch up.
I agree with your comments below, and believe that Dan's async scrubbing
updates fix these, in that we don't throw away results from a system
initiated ARS.
Let me know if you had any more questions.
Thanks,
-Vishal
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
parent reply other threads:[~2016-03-02 1:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <56BE64E1.1080500@hpe.com>]
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=1456883236.4525.12.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=linda.knippers@hpe.com \
--cc=linux-nvdimm@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox