From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: geoff@infradead.org, panand@redhat.com, horms@verge.net.au,
kexec@lists.infradead.org
Subject: Re: [PATCH v7 01/10] kexec: exntend the semantics of kexec_iomem_for_each_line
Date: Mon, 22 May 2017 09:18:07 +0900 [thread overview]
Message-ID: <20170522001806.GA6544@linaro.org> (raw)
In-Reply-To: <1495064224.19471.13.camel@infradead.org>
On Wed, May 17, 2017 at 04:37:04PM -0700, David Woodhouse wrote:
> On Wed, 2017-05-17 at 14:51 +0900, AKASHI Takahiro wrote:
> > The current kexec_iomem_for_each_line() counts up all the lines for which
> > a callback function returns zero(0) or positive, and otherwise it stops
> > further scanning.
> > This behavior is incovenient in some cases. For instance, on arm64, we want
> > to count up "System RAM" entries, but need to skip "reserved" entries.
>
> s/exntend/extend/ and s/incovenient/inconvenient/ but other than that,
> all ten patches
> Tested-by: David Woodhouse <dwmw@amazon.co.uk>
Thanks a lot!
> Simon, any chance of a 2.0.15 release once these are merged please?
For your convenience, you can also find my patch with fixes above:
http://git.linaro.org/people/takahiro.akashi/kexec-tools.git
> Thanks for your continued effort on this, Akashi-san. Congratulations
> on finally getting the support merged into 4.12!
>
> I've backported the final set of patches to 4.9 too. That's where I'm
> going to be using it for the moment. In case it's useful to anyone
> else, it's here:
> http://git.infradead.org/users/dwmw2/arm64-kdump-4.9.git
Great.
Just FYI, we, linaro, will also backport kdump to our lsk v4.4 and v4.9.
Thanks,
-Takahiro AKASHI
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-05-22 0:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 5:51 [PATCH v7 00/10] (kexec-tools) arm64: add kdump support AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 01/10] kexec: exntend the semantics of kexec_iomem_for_each_line AKASHI Takahiro
2017-05-17 23:37 ` David Woodhouse
2017-05-22 0:18 ` AKASHI Takahiro [this message]
2017-05-22 11:41 ` Simon Horman
2017-05-17 5:51 ` [PATCH v7 02/10] kexec: generalize and rename get_kernel_stext_sym() AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 03/10] arm64: identify PHYS_OFFSET correctly AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 04/10] arm64: change return values on error to negative AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 05/10] arm64: kdump: identify memory regions AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 06/10] arm64: kdump: add elf core header segment AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 07/10] arm64: kdump: set up kernel image segment AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 08/10] arm64: kdump: set up other segments AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 09/10] arm64: kdump: add DT properties to crash dump kernel's dtb AKASHI Takahiro
2017-05-17 5:51 ` [PATCH v7 10/10] arm64: kdump: Add support for binary image files AKASHI Takahiro
2017-05-22 6:22 ` [PATCH v7 00/10] (kexec-tools) arm64: add kdump support Pratyush Anand
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=20170522001806.GA6544@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=dwmw2@infradead.org \
--cc=geoff@infradead.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=panand@redhat.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