From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Hannes Eder <hannes@hanneseder.net>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, Yinghai Lu <yinghai@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] x86: cleanup patches 20090322
Date: Mon, 23 Mar 2009 16:22:40 +0530 [thread overview]
Message-ID: <1237805560.2630.16.camel@ht.satnam> (raw)
In-Reply-To: <154e089b0903230335q1fbdcc4biea140738b01e7a36@mail.gmail.com>
On Mon, 2009-03-23 at 11:35 +0100, Hannes Eder wrote:
> On Mon, Mar 23, 2009 at 10:45 AM, Jaswinder Singh Rajput
> <jaswinder@kernel.org> wrote:
> > On Mon, 2009-03-23 at 18:45 +1030, Rusty Russell wrote:
> >> On Monday 23 March 2009 07:22:56 Jaswinder Singh Rajput wrote:
> >> > x86: e820.h fix various signedness issues in setup.c and e820.c
> >>
> >> Wouldn't fixing the users be better than changing the header? Esp. since
> >> it could well now cause similar warnings in userspace programs.
> >>
> >> > struct e820map {
> >> > - __u32 nr_map;
> >> > + __s32 nr_map;
> >> > struct e820entry map[E820_X_MAX];
> >> > };
> >>
> >> This number can't be negative!
> >>
> >
> > Is this OK, or should I go more further:
>
> since sanitize_e820_map does only modify its third argument on
> success, and leaves it untouched on error, the temporary variable
> could be eliminated in some places.
OK, this is different issue so I will send this in separate patch.
Thanks,
--
JSR
next prev parent reply other threads:[~2009-03-23 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 20:52 [git-pull -tip] x86: cleanup patches 20090322 Jaswinder Singh Rajput
2009-03-23 8:15 ` Rusty Russell
2009-03-23 9:45 ` Jaswinder Singh Rajput
2009-03-23 10:35 ` Hannes Eder
2009-03-23 10:52 ` Jaswinder Singh Rajput [this message]
2009-03-23 21:10 ` Rusty Russell
2009-03-23 21:16 ` Sam Ravnborg
2009-03-23 10:07 ` Jaswinder Singh Rajput
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=1237805560.2630.16.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=hannes@hanneseder.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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