From: Dan Williams <dan.j.williams@intel.com>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux MM <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Allow EINJ to inject memory error to NVDIMM
Date: Fri, 23 Oct 2015 12:05:56 -0700 [thread overview]
Message-ID: <CAPcyv4gj-UXUB52B6sU37w4qtdND9zbxijVQqGg9Kxa9=RNOvg@mail.gmail.com> (raw)
In-Reply-To: <1445626439-8424-1-git-send-email-toshi.kani@hpe.com>
On Fri, Oct 23, 2015 at 11:53 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> This patch-set extends the EINJ driver to allow injecting a memory
> error to NVDIMM. It first extends iomem resource interface to support
> checking a NVDIMM region.
>
> Patch 1/3 changes region_intersects() to accept non-RAM regions, and
> adds region_intersects_ram().
>
> Patch 2/3 adds region_intersects_pmem() to check a NVDIMM region.
>
> Patch 3/3 changes the EINJ driver to allow injecting a memory error
> to NVDIMM.
>
> ---
> v2:
> - Change the EINJ driver to call region_intersects_ram() for checking
> RAM with a specified size. (Dan Williams)
> - Add export to region_intersects_ram().
>
> ---
For the series:
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-10-23 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 18:53 Toshi Kani
2015-10-23 18:53 ` [PATCH v2 1/3] resource: Add @flags to region_intersects() Toshi Kani
2015-10-23 18:53 ` [PATCH v2 2/3] resource: Add region_intersects_pmem() Toshi Kani
2015-10-23 18:53 ` [PATCH v2 3/3] ACPI/APEI/EINJ: Allow memory error injection to NVDIMM Toshi Kani
2015-10-24 15:24 ` Rafael J. Wysocki
2015-10-25 10:45 ` Borislav Petkov
2015-10-26 14:52 ` Toshi Kani
2015-10-23 19:05 ` Dan Williams [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='CAPcyv4gj-UXUB52B6sU37w4qtdND9zbxijVQqGg9Kxa9=RNOvg@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=rjw@rjwysocki.net \
--cc=toshi.kani@hpe.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