From: Baoquan He <bhe@redhat.com>
To: Simon Horman <horms@verge.net.au>
Cc: andrew.cooper3@citrix.com, daniel.kiper@oracle.com,
Eric DeVolder <eric.devolder@oracle.com>,
kexec@lists.infradead.org, konrad.wilk@oracle.com
Subject: Re: [PATCH] Handle additional e820 memmap type strings
Date: Tue, 23 May 2017 22:08:25 +0800 [thread overview]
Message-ID: <20170523140825.GE2295@x1> (raw)
In-Reply-To: <20170522114351.GF16822@verge.net.au>
On 05/22/17 at 01:43pm, Simon Horman wrote:
> On Fri, May 19, 2017 at 05:15:38PM +0800, Baoquan He wrote:
> > On 05/17/17 at 07:51am, Eric DeVolder wrote:
> > > > > diff --git a/kexec/firmware_memmap.c b/kexec/firmware_memmap.c
> > > > > index 4d84f00..1ee214a 100644
> > > > > --- a/kexec/firmware_memmap.c
> > > > > +++ b/kexec/firmware_memmap.c
> > > > > @@ -164,6 +164,10 @@ static int parse_memmap_entry(const char *entry, struct memory_range *range)
> > > > > range->type = RANGE_RESERVED;
> > > > > else if (strcmp(type, "reserved") == 0)
> > > > > range->type = RANGE_RESERVED;
> > > > > + else if (strcmp(type, "Reserved") == 0)
> > > > > + range->type = RANGE_RESERVED;
> > > > > + else if (strcmp(type, "Unknown E820 type") == 0)
> > > > > + range->type = RANGE_RESERVED;
> > > >
> > > > Should we change the "reserved" one to "Reserved" so that we don't need
> > > > to have "reserved" and "Reserved" at the same time?
> > >
> > > The lower-case "reserved" has been in use by the kernel for quite a long
> > > while, and upper-case "Reserved" has been recently introduced. I think
> > > removing lower-case "reserved" would result in problems with existing,
> > > older, kernels that still would be using "reserved".
> >
> > Thanks. Then it looks good to me. Ack.
> >
> > Simon might pick several patches one time every several days. Please
> > wait.
>
> Yes, I try to pick up new patches within a few working days.
> I have applied this one.
Thanks, Simon!
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-05-23 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 16:03 [PATCH] Handle additional e820 memmap type strings Eric DeVolder
2017-05-14 23:28 ` Eric DeVolder
2017-05-15 14:07 ` Baoquan He
2017-05-17 12:51 ` Eric DeVolder
2017-05-19 9:15 ` Baoquan He
2017-05-22 11:43 ` Simon Horman
2017-05-23 14:08 ` Baoquan He [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=20170523140825.GE2295@x1 \
--to=bhe@redhat.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=eric.devolder@oracle.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.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