linux-kernel - Re: [PATCH V2] staging: fbtft: fix all print warnings reported by sparse

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150430144001.GA13321@kroah.com>
Date:	Thu, 30 Apr 2015 16:40:01 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Marcus Folkesson <marcus.folkesson@...il.com>
Cc:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	noralf@...nnes.org, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] staging: fbtft: fix all print warnings reported by
 sparse

On Fri, Apr 10, 2015 at 03:45:50PM +0200, Marcus Folkesson wrote:
> Warnings reported by sparse:
> 
> drivers/staging/fbtft/fbtft-core.c:1004:4: warning: format ‘%d’ expects
> argument of type ‘int’, but argument 3 has type ‘size_t’ [-Wformat=]
>     par->txbuf.len >> 10, par->txbuf.dma ? "DMA " : "");
> 
> drivers/staging/fbtft/fbtft-io.c:63:4: warning: format ‘%d’ expects
> argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
>     __func__, len);
> 
> drivers/staging/fbtft/fbtft-io.c:110:5: warning: format ‘%d’ expects
> argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
>      __func__, len);
> 
> Signed-off-by: Marcus Folkesson <marcus.folkesson@...il.com>
> ---
>  drivers/staging/fbtft/fbtft-core.c | 2 +-
>  drivers/staging/fbtft/fbtft-io.c   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)

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