Re: [PATCH] mpparse.c:231: warning: comparison is always false

On Thu, Sep 14, 2006 at 02:35:42AM -0400, Dave Jones wrote:
...  
> Yes, I understand your patch. What I don't understand is why summit/generic
> have this set so high in the first place.

Sorry for misunderstanding your understanding...
I simply tried to understand another question (how this warning
could be tolerated for all those gits?).

Jarek P.  
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] mpparse.c:231: warning: comparison is always false
  - From: Jarek Poplawski <[email protected]>
- Re: [PATCH] mpparse.c:231: warning: comparison is always false
  - From: Dave Jones <[email protected]>
- Re: [PATCH] mpparse.c:231: warning: comparison is always false
  - From: Jarek Poplawski <[email protected]>
- Re: [PATCH] mpparse.c:231: warning: comparison is always false
  - From: Dave Jones <[email protected]>

Prev by Date: Re: Assignment of GDT entries
Next by Date: Re: [linux-pm] OpPoint summary
Previous by thread: Re: [PATCH] mpparse.c:231: warning: comparison is always false
Next by thread: Re: [PATCH] mpparse.c:231: warning: comparison is always false
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]