From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/1] xen:include:asm-x86:e820: just covert nr_map with unsigned int
Date: Fri, 08 Aug 2014 15:54:15 +0800 [thread overview]
Message-ID: <53E48227.9000300@intel.com> (raw)
In-Reply-To: <53E49A87020000780002A635@mail.emea.novell.com>
On 2014/8/8 15:38, Jan Beulich wrote:
>>>> On 08.08.14 at 09:26, <tiejun.chen@intel.com> wrote:
>> On 2014/8/8 15:15, Jan Beulich wrote:
>>>>>> On 08.08.14 at 09:00, <tiejun.chen@intel.com> wrote:
>>>> This shouldn't ever be negative.
>>>
>>> This means nothing for the actual change, and makes me imply you did
>>> the change without checking it actually _is_ never negative in any of
>>> the uses.
>>>
>>> Also please cut down your patch title prefixes (not just here) to
>>> something reasonable.
>>>
>>
>> What about this?
>>
>> xen:e820map: just convert nr_map with unsigned int
>
> x86: make struct e820map's nr_map unsigned
Okay.
>
>> nr_map is used to represent the amount of e820entry in e820 so it
>> shouldn't be negative.
>
> You still say "shouldn't" instead of "isn't", making me still imply you
> didn't verify that fact. I.e. I'd be fine with a suitable variant of the
Maybe I'm poor to describe that main point here.
x86: make struct e820map's nr_map unsigned
nr_map is used to represent the amount of e820entry in e820 so its
not always negative.
Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
Thanks
Tiejun
> earlier more terse description as long as it says what it needs to say.
>
> Jan
>
>
>
next prev parent reply other threads:[~2014-08-08 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 7:00 [PATCH 1/1] xen:include:asm-x86:e820: just covert nr_map with unsigned int Tiejun Chen
2014-08-08 7:15 ` Jan Beulich
2014-08-08 7:26 ` Chen, Tiejun
2014-08-08 7:38 ` Jan Beulich
2014-08-08 7:54 ` Chen, Tiejun [this message]
2014-08-08 8:49 ` Jan Beulich
2014-08-08 9:06 ` Chen, Tiejun
2014-08-08 9:18 ` Jan Beulich
2014-08-08 9:31 ` Chen, Tiejun
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=53E48227.9000300@intel.com \
--to=tiejun.chen@intel.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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).