From: Borislav Petkov <bp@alien8.de>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
rafael.j.wysocki@intel.com, dan.j.williams@intel.com,
dyoung@redhat.com, x86@kernel.org, linux-ia64@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
kexec@lists.infradead.org, xen-devel@lists.xenproject.org,
linux-samsung-soc@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, linux-nvdimm@lists.01.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/17] Enhance iomem search interfaces and support EINJ to NVDIMM
Date: Mon, 25 Jan 2016 19:18:04 +0000 [thread overview]
Message-ID: <20160125191804.GE14030@pd.tnic> (raw)
In-Reply-To: <1452020068-26492-1-git-send-email-toshi.kani@hpe.com>
On Tue, Jan 05, 2016 at 11:54:28AM -0700, Toshi Kani wrote:
> This patch-set enhances the iomem table and its search interfacs, and
> then changes EINJ to support NVDIMM.
>
> - Patches 1-2 add a new System RAM type, IORESOURCE_SYSTEM_RAM, and
> make the iomem search interfaces work with resource flags with
> modifier bits set. IORESOURCE_SYSTEM_RAM has IORESOURCE_MEM bit set
> for backward compatibility.
>
> - Patch 3 adds a new field, I/O resource descriptor, into struct resource.
> Drivers can assign their unique descritor to a range when they support
> the iomem search interfaces.
>
> - Patches 4-9 changes initializations of resource entries. They set
> the System RAM type to System RAM ranges, set I/O resource descriptors
> to the regions targeted by the iomem search interfaces, and change
> to call kzalloc() where kmalloc() is used to allocate struct resource
> ranges.
>
> - Patches 10-14 extend the iomem interfaces to check System RAM ranges
> with the System RAM type and the I/O resource descriptor.
>
> - Patch 15-16 remove deprecated walk_iomem_res().
>
> - Patch 17 changes the EINJ driver to allow injecting a memory error
> to NVDIMM.
Ok, all applied ontop of 4.5-rc1.
You could take a look if everything's still fine and I haven't botched
anything:
http://git.kernel.org/cgit/linux/kernel/git/bp/bp.git/log/?h=tip-mm
I'll let the build bot chew on it and then test it here and send it out
again to everyone on CC so that people don't act surprised.
Thanks for this cleanup, code looks much better now!
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-01-25 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 18:54 [PATCH v3 00/17] Enhance iomem search interfaces and support EINJ to NVDIMM Toshi Kani
2016-01-25 19:18 ` Borislav Petkov [this message]
2016-01-25 21:34 ` Toshi Kani
2016-01-25 21:49 ` Borislav Petkov
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=20160125191804.GE14030@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hpe.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).