On Sun, 2006-02-26 at 22:56 +0100, Jesper Juhl wrote: > Yeah so gcc is not perfect, but that still doesn't change that the > intention of the warning and the use of the word "might" is as I said > above. Not a very compelling case for changing the kernel rather than getting GCC fixed. Lee - 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/
- Follow-Ups:
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- From: "Jesper Juhl" <[email protected]>
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- References:
- Building 100 kernels; we suck at dependencies and drown in warnings
- From: Jesper Juhl <[email protected]>
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- From: Lee Revell <[email protected]>
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- From: Nix <[email protected]>
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- From: "Jesper Juhl" <[email protected]>
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- From: Lee Revell <[email protected]>
- Re: Building 100 kernels; we suck at dependencies and drown in warnings
- From: "Jesper Juhl" <[email protected]>
- Building 100 kernels; we suck at dependencies and drown in warnings
- Prev by Date: Re: Building 100 kernels; we suck at dependencies and drown in warnings
- Next by Date: Re: old radeon latency problem still unfixed?
- Previous by thread: Re: Building 100 kernels; we suck at dependencies and drown in warnings
- Next by thread: Re: Building 100 kernels; we suck at dependencies and drown in warnings
- Index(es):
 |