From: Simon Horman <horms@verge.net.au>
To: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH 1/2] kexec,x86: remove duplicate get_memory_ranges
Date: Wed, 30 Jan 2013 13:16:20 +0900 [thread overview]
Message-ID: <20130130041620.GI28230@verge.net.au> (raw)
In-Reply-To: <50F4E162.7020908@cn.fujitsu.com>
On Tue, Jan 15, 2013 at 12:56:02PM +0800, Zhang Yanfei wrote:
> 于 2013年01月11日 16:57, Zhang Yanfei 写道:
> > At first, we have already filled the kexec_info.memory_ranges by
> > calling my_load() -> get_memory_ranges(). So if we want to
> > get the memory information, we could just use the existing
> > one instead of calling get_memory_ranges again.
> >
> > Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
>
> ping...
Sorry for the extended delay. Applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-01-30 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 8:57 [PATCH 1/2] kexec,x86: remove duplicate get_memory_ranges Zhang Yanfei
2013-01-11 8:58 ` [PATCH 2/2] kexec: add additional check when getting memory info Zhang Yanfei
2013-01-30 4:16 ` Simon Horman
2013-01-15 4:56 ` [PATCH 1/2] kexec,x86: remove duplicate get_memory_ranges Zhang Yanfei
2013-01-30 4:16 ` Simon Horman [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=20130130041620.GI28230@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=zhangyanfei@cn.fujitsu.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