public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Eric Anholt <eric@anholt.net>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Wed, 1 Nov 2017 10:58:37 +0100	[thread overview]
Message-ID: <20171101105837.75bc2be5@bbrezillon> (raw)
In-Reply-To: <20171101141640.3ca7597f@canb.auug.org.au>

Hi Stephen,

On Wed, 1 Nov 2017 14:16:40 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Dave,
> 
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
> 
> drivers/gpu/drm/vc4/vc4_bo.c: In function 'vc4_bo_stats_debugfs':
> drivers/gpu/drm/vc4/vc4_bo.c:91:17: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
>    seq_printf(m, "%30s: %6dkb BOs (%d)\n", "userspace BO cache",
>                  ^
> drivers/gpu/drm/vc4/vc4_bo.c:95:17: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
>    seq_printf(m, "%30s: %6dkb BOs (%d)\n", "total purged BO",
>                  ^
> 
> Introduced by commit
> 
>   b9f19259b84d ("drm/vc4: Add the DRM_IOCTL_VC4_GEM_MADVISE ioctl")
> 

Just sent a patch fixing the problem.

Thanks for the report.

Boris

  reply	other threads:[~2017-11-01  9:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  3:16 linux-next: build warnings after merge of the drm tree Stephen Rothwell
2017-11-01  9:58 ` Boris Brezillon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-06  4:11 Stephen Rothwell
2025-12-16  1:04 ` Stephen Rothwell
2025-11-06  4:05 Stephen Rothwell
2025-11-06  4:03 Stephen Rothwell
2025-01-13  5:03 Stephen Rothwell
2024-02-19  5:21 Stephen Rothwell
2023-06-13  6:29 Stephen Rothwell
2023-01-05  3:47 Stephen Rothwell
2021-06-03  9:32 Stephen Rothwell
2021-07-08  2:20 ` Stephen Rothwell
2021-08-10  9:26   ` Stephen Rothwell
2021-08-10 10:14     ` Daniel Vetter
2021-08-10 10:38       ` Stephen Rothwell
2021-08-10 10:50         ` Daniel Vetter
2021-08-10 11:01           ` Stephen Rothwell
2021-08-10 12:39             ` Daniel Vetter
2021-08-10 13:21               ` Stephen Rothwell
2021-04-01  7:32 Stephen Rothwell
2021-04-21  6:30 ` Stephen Rothwell
2020-11-05  6:50 Stephen Rothwell
2020-11-15 23:44 ` Stephen Rothwell
2020-12-14 19:50   ` Stephen Rothwell
2020-12-15  2:47     ` Stephen Rothwell
2020-12-15  9:42       ` Daniel Vetter
2017-05-19  2:07 Stephen Rothwell
2017-05-19 17:49 ` Eric Anholt
2017-05-25  1:49   ` Stephen Rothwell
2017-06-02  3:59     ` Stephen Rothwell
2017-06-02 21:05       ` Eric Anholt
2017-06-02 23:40         ` Stephen Rothwell
2017-06-03  0:45           ` Eric Anholt
2017-06-03  1:26             ` Stephen Rothwell
2017-02-23 23:27 Stephen Rothwell
2017-02-19 23:48 Stephen Rothwell
2012-10-04  2:21 Stephen Rothwell
2012-09-04  3:58 Stephen Rothwell
2012-09-04  5:31 ` Guenter Roeck
2012-09-04  6:40 ` Sedat Dilek
2012-09-04  8:22   ` Dave Airlie
2012-09-04  8:58     ` Sedat Dilek

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=20171101105837.75bc2be5@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=airlied@linux.ie \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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