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]
Date:   Wed, 1 Nov 2017 11:19:59 -0400
From:   Rob Clark <robdclark@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jordan Crouse <jcrouse@...eaurora.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: linux-next: build warning after merge of the drm-msm tree

On Tue, Oct 31, 2017 at 11:46 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Rob,
>
> After merging the drm-msm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> In file included from include/drm/drm_mm.h:49:0,
>                  from include/drm/drmP.h:73,
>                  from drivers/gpu/drm/msm/msm_drv.h:37,
>                  from drivers/gpu/drm/msm/msm_gpu.h:24,
>                  from drivers/gpu/drm/msm/msm_gpu.c:18:
> drivers/gpu/drm/msm/msm_gpu.c: In function 'msm_gpu_init':
> drivers/gpu/drm/msm/msm_gpu.c:780:31: warning: format '%lu' expects argument of type 'long unsigned int', but argument 7 has type 'unsigned int' [-Wformat=]
>    DRM_DEV_INFO_ONCE(drm->dev, "Only creating %lu ringbuffers\n",
>                                ^
> include/drm/drm_print.h:237:60: note: in definition of macro 'DRM_DEV_INFO'
>   drm_dev_printk(dev, KERN_INFO, DRM_UT_NONE, __func__, "", fmt, \
>                                                             ^
> drivers/gpu/drm/msm/msm_gpu.c:780:3: note: in expansion of macro 'DRM_DEV_INFO_ONCE'
>    DRM_DEV_INFO_ONCE(drm->dev, "Only creating %lu ringbuffers\n",
>    ^
>
> Introduced by commit
>
>   f97decac5f4c ("drm/msm: Support multiple ringbuffers")

Oh, I thought Arnd fixed[1] that already, but it looks like I lost his
patch in the process of moving to a newer version of the
multiple-ringbuffers patch.

I've added Arnd's patch to msm-next.


[1] https://patchwork.freedesktop.org/patch/170111/

Powered by blists - more mailing lists