From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
Tony Luck <tony.luck@intel.com>,
David Hildenbrand <dahi@linux.vnet.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] s390/crash_dump: Use for_each_mem_range
Date: Fri, 18 Sep 2015 13:17:50 +0200 [thread overview]
Message-ID: <20150918111750.GA3986@osiris> (raw)
In-Reply-To: <1442343264-10583-1-git-send-email-kuleshovmail@gmail.com>
On Wed, Sep 16, 2015 at 12:54:24AM +0600, Alexander Kuleshov wrote:
> The <linux/memblock.h> already provides for_each_mem_range() macro that
> iterates through memblock areas from type_a and not included in type_b.
> We can remove custom for_each_dump_mem_range() macro and use the
> for_each_mem_range() instead.
>
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
> ---
> arch/s390/kernel/crash_dump.c | 16 ++++------------
> 1 file changed, 4 insertions(+), 12 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2015-09-18 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 18:54 [PATCH 1/2] s390/crash_dump: Use for_each_mem_range Alexander Kuleshov
2015-09-18 11:17 ` Heiko Carstens [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=20150918111750.GA3986@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@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 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.