linux-mips
[Top] [All Lists]

Re: sparse and mips

To: Jeroen Vreeken <pe1rxq@amsat.org>
Subject: Re: sparse and mips
From: Ralf Baechle <ralf@linux-mips.org>
Date: Mon, 28 Feb 2005 12:11:20 +0000
Cc: linux-mips@linux-mips.org
In-reply-to: <422256A3.2030407@amsat.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <422256A3.2030407@amsat.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Mon, Feb 28, 2005 at 12:24:19AM +0100, Jeroen Vreeken wrote:

> I tried compiling my switch driver with sparse to see if I did some 
> stupid casts and got a lot of warnings.... (attached below)
> Are others using sparse with mips kernels and getting the same?
> Or has nobody taken the time to fix it up?
> (The byteorder stuff should creap up everywhere or not?)

Not to my knowledge.  I always meant to as a preventive maintenance meassure
but somehow there was always something more important to do ...

> include/asm/byteorder.h:27:4: warning: "MIPS, but neither __MIPSEB__, 
> nor __MIPSEL__???"
> include/linux/kernel.h:200:2: warning: "Please fix asm/byteorder.h"

A result of sparse not knowing about MIPS yet.

> include/linux/aio_abi.h:59:2: warning: edit for your odd byteorder.

Same.

The others don't really make sense at the first look.

73,

  Ralf

<Prev in Thread] Current Thread [Next in Thread>