DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding;
        b=dLUgF4gf+UfqjT0lFjSlXxK9JCzrdD+6P3/+modIvn1x29l9zFaEXbUmKEMtZ2OpiwlB03fbj+l3nCdAPGQW/CAbMqdABfFVgGiAkk17chGzIDRaVhj2t3NTb5fR/yV8o0fYHEcupHp82pikDoPb5+jEqtZNrO5nTpqTXmqtclc=
Subject: Re: sparse - make __CHECK_ENDIAN__ default enabled?
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <20080220220326.GA22328@uranus.ravnborg.org>
References: <20080220220326.GA22328@uranus.ravnborg.org>
Content-Type: text/plain
Date: Wed, 20 Feb 2008 14:39:46 -0800
Message-Id: <1203547186.25307.52.camel@brick>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 841
Lines: 24

On Wed, 2008-02-20 at 23:03 +0100, Sam Ravnborg wrote:
> Hi Harvey.
> 
> Can I ask you to look into the worst offenders so we
> can make -D__CHECK_ENDIAN__ enabled per default
> in the kernel.
> Or maybe we should do it anyway?

>From a quick test, the same places that spew sparse warnings, spew
lots more sparse warnings, the places that are not so bad....are not
so bad afterwards either.

There's still so many of the trivial warnings that maybe it's not the
right time for this yet.  Ask me again when we get to the 2.6.26
timeframe, we'll see how many I've gotten rid of by then.

Harvey


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