DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=QiDsq0qqdXbqTsMvFWHQYpWsi9MkwxjKIj1XjkE0PQvkQfqbUWwVnfzm2Uwa0b4R4J
         HOfHa81o9X8/y9CNd5oZN7l+1fyF6vqgPJtf/CLN7W4lJ6o/vxj2zONViRN7EPYostZ3
         AjlyUz2qcFE3eGZRSSrY6MH8ZnoNjT6B7XsvQ=
Message-ID: <4CF434B6.3030503@gmail.com>
Date: Tue, 30 Nov 2010 00:18:14 +0100
From: Jiri Slaby <jirislaby@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.2.12) Gecko/20101026 SUSE/3.1.6 Thunderbird/3.1.6
MIME-Version: 1.0
To: Randy Dunlap <randy.dunlap@oracle.com>
CC: =?ISO-8859-1?Q?Peter_H=FCwe?= <PeterHuewe@gmx.de>,
        devel@driverdev.osuosl.org, Greg Kroah-Hartman <gregkh@suse.de>,
        linux-kernel@vger.kernel.org, Mark Allyn <mark.a.allyn@intel.com>,
        Joe Perches <joe@perches.com>, Ben Hutchings <ben@decadent.org.uk>,
        Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 3/3] staging/sep: Fix sparse printk format warning
References: <1291066280-19126-1-git-send-email-peterhuewe@gmx.de>	<1291066280-19126-3-git-send-email-peterhuewe@gmx.de>	<20101129134943.4ef92448.randy.dunlap@oracle.com>	<201011292259.12527.PeterHuewe@gmx.de> <20101129140131.9dd954a9.randy.dunlap@oracle.com>
In-Reply-To: <20101129140131.9dd954a9.randy.dunlap@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 24

On 11/29/2010 11:01 PM, Randy Dunlap wrote:
> On Mon, 29 Nov 2010 22:59:11 +0100 Peter H?we wrote:
> 
>>> Are you sure?  I'm used to these being gcc warnings, not sparse.
>> You're right - these are generated by gcc ;) sorry for the confusion.
>>
>>> Also, this fixes the warnings on x86_64 but not on x86_32/i386:
>> You're right again, I'm on x86_64 - so what should I use instead?
> 
> I dunno, I've tried to fix this myself and the only thing that I have
> been successful with is casting those ioctl values to (unsigned long)
> and using %lx to print them.

What about to remove that completely :)? I don't see what that could be
good for -- everybody from userspace can print it...

regards,
-- 
js
--
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/