All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Paul Jackson <pj@sgi.com>
Cc: David Ford <david+challenge-response@blue-labs.org>,
	linux-kernel@vger.kernel.org
Subject: Re: warning: comparison is always false due to limited range of data type
Date: 8 Aug 2004 16:21:07 +0200
Date: Sun, 8 Aug 2004 16:21:07 +0200	[thread overview]
Message-ID: <20040808142107.GB94449@muc.de> (raw)
In-Reply-To: <20040807174133.1e368fbc.pj@sgi.com>

On Sat, Aug 07, 2004 at 05:41:33PM -0700, Paul Jackson wrote:
> david+challenge-response@blue-labs.org wrote:
> > fs/smbfs/inode.c:563: warning: comparison is always false due to limited 
> > range of data type
> > fs/smbfs/inode.c:564: warning: comparison is always false due to limited 
> > range of data type
> 
> You're lucky you're still on the cc list David - please don't use reply
> addresses that require editing.
> 
> Adding Andi Kleen <ak@muc.de> to cc list - looks from the bk log that he
> might have some interest in this.

Sorry, I forgot what I changed here. At least my original
changes didn't cause warnings as far as I know. Someone else please
take care of it.

-Andi

> 
> fs/smbfs/inode.c
>   1.46 03/12/01 07:04:55 ak@muc.de[torvalds] +2 -2
>   UID16 fixes
> 
> bk diffs -r1.45..1.46 fs/smbfs/inode.c
> ===== fs/smbfs/inode.c 1.45 vs 1.46 =====
> 554,555c554,555
> <               mnt->uid = OLD_TO_NEW_UID(oldmnt->uid);
> <               mnt->gid = OLD_TO_NEW_GID(oldmnt->gid);
> ---
> >               SET_UID(mnt->uid, oldmnt->uid);
> >               SET_GID(mnt->gid, oldmnt->gid);
> 
> -- 
>                           I won't rest till it's the best ...
>                           Programmer, Linux Scalability
>                           Paul Jackson <pj@sgi.com> 1.650.933.1373

  parent reply	other threads:[~2004-08-08 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07 23:17 warning: comparison is always false due to limited range of data type David Ford
2004-08-08  0:41 ` Paul Jackson
2004-08-08  1:09   ` [OT] " David Ford
2004-08-08  1:52     ` Paul Jackson
2004-08-08 14:21   ` Andi Kleen [this message]
2004-08-09  2:37     ` Paul Jackson
2004-08-09 21:42       ` Paul Jackson
     [not found] <2qIDQ-7ZR-13@gated-at.bofh.it>
     [not found] ` <2qK2T-oz-1@gated-at.bofh.it>
     [not found]   ` <2qWQx-Hi-7@gated-at.bofh.it>
     [not found]     ` <2r8oA-ks-1@gated-at.bofh.it>
     [not found]       ` <20040818225304.GF22559@bouh.is-a-geek.org>
2004-08-18 23:14         ` Paul Jackson

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=20040808142107.GB94449@muc.de \
    --to=ak@muc.de \
    --cc=david+challenge-response@blue-labs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.