public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	noralf@tronnes.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] staging: fbtft: fix all print warnings reported by sparse
Date: Thu, 30 Apr 2015 16:40:01 +0200	[thread overview]
Message-ID: <20150430144001.GA13321@kroah.com> (raw)
In-Reply-To: <1428673550-5890-2-git-send-email-marcus.folkesson@gmail.com>

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@gmail.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 :(

      reply	other threads:[~2015-04-30 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 19:31 [PATCH] staging: fbtft: fix all print warnings reported by sparse Marcus Folkesson
2015-04-10 13:21 ` Greg Kroah-Hartman
2015-04-10 13:45 ` Changelog: " Marcus Folkesson
2015-04-10 13:45   ` [PATCH V2] " Marcus Folkesson
2015-04-30 14:40     ` Greg Kroah-Hartman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150430144001.GA13321@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus.folkesson@gmail.com \
    --cc=noralf@tronnes.org \
    --cc=thomas.petazzoni@free-electrons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox