From: Joe Perches <joe@perches.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org,
Mark Hemment <markhe@nextd.demon.co.uk>,
Andrea Arcangeli <andrea@e-mind.com>,
Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [PATCH] mm/slab.c remove impossible <0 check - size_t is not signed - patch is against 2.6.1-rc1-mm2
Date: Wed, 07 Jan 2004 19:08:14 -0800 [thread overview]
Message-ID: <1073531294.2304.18.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.56.0401080204060.9700@jju_lnx.backbone.dif.dk>
On Wed, 2004-01-07 at 17:20, Jesper Juhl wrote:
> size_t is an unsigned datatype in all archs.
There are literally hundreds of these in the code.
Compile with -W -Wall and see for yourself.
next prev parent reply other threads:[~2004-01-08 3:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 1:20 [PATCH] mm/slab.c remove impossible <0 check - size_t is not signed - patch is against 2.6.1-rc1-mm2 Jesper Juhl
2004-01-08 3:08 ` Joe Perches [this message]
2004-01-08 9:33 ` Jesper Juhl
2004-01-08 10:16 ` Paul Jackson
2004-01-08 15:28 ` Jens Axboe
2004-01-08 19:33 ` Manfred Spraul
2004-01-08 15:37 ` Joe Perches
2004-01-15 1:13 ` Bill Davidsen
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=1073531294.2304.18.camel@localhost.localdomain \
--to=joe@perches.com \
--cc=andrea@e-mind.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=markhe@nextd.demon.co.uk \
/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).