All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <treding@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: linux-next: build warnings after merge of the drm-misc tree
Date: Fri, 14 Aug 2015 14:51:20 +0200	[thread overview]
Message-ID: <20150814125119.GC22537@ulmo.nvidia.com> (raw)
In-Reply-To: <20150814153532.78cd6e88@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 1276 bytes --]

On Fri, Aug 14, 2015 at 03:35:32PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the drm-misc tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
> 
> drivers/gpu/drm/exynos/exynos_drm_drv.c:290:2: warning: initialization from incompatible pointer type
>   .get_vblank_counter = drm_vblank_count,
>   ^
> drivers/gpu/drm/exynos/exynos_drm_drv.c:290:2: warning: (near initialization for 'exynos_drm_driver.get_vblank_counter')
> drivers/gpu/drm/rcar-du/rcar_du_drv.c:262:2: warning: initialization from incompatible pointer type
>   .get_vblank_counter = drm_vblank_count,
>   ^
> drivers/gpu/drm/rcar-du/rcar_du_drv.c:262:2: warning: (near initialization for 'rcar_du_driver.get_vblank_counter')
> drivers/gpu/drm/msm/msm_drv.c:981:2: warning: initialization from incompatible pointer type
>   .get_vblank_counter = drm_vblank_count,
>   ^
> drivers/gpu/drm/msm/msm_drv.c:981:2: warning: (near initialization for 'msm_driver.get_vblank_counter')
> 
> Introduced by commit
> 
>   b90180b057f7 ("drm/irq: More pipe/crtc consistency cleanups")

Yes, that patch turned out to be incomplete. Daniel suggested to remove
it from drm-misc for now and I'll address this fully in a larger patch
for 4.4.

Thierry

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <treding@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	<intel-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>, <linux-next@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the drm-misc tree
Date: Fri, 14 Aug 2015 14:51:20 +0200	[thread overview]
Message-ID: <20150814125119.GC22537@ulmo.nvidia.com> (raw)
In-Reply-To: <20150814153532.78cd6e88@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

On Fri, Aug 14, 2015 at 03:35:32PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the drm-misc tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
> 
> drivers/gpu/drm/exynos/exynos_drm_drv.c:290:2: warning: initialization from incompatible pointer type
>   .get_vblank_counter = drm_vblank_count,
>   ^
> drivers/gpu/drm/exynos/exynos_drm_drv.c:290:2: warning: (near initialization for 'exynos_drm_driver.get_vblank_counter')
> drivers/gpu/drm/rcar-du/rcar_du_drv.c:262:2: warning: initialization from incompatible pointer type
>   .get_vblank_counter = drm_vblank_count,
>   ^
> drivers/gpu/drm/rcar-du/rcar_du_drv.c:262:2: warning: (near initialization for 'rcar_du_driver.get_vblank_counter')
> drivers/gpu/drm/msm/msm_drv.c:981:2: warning: initialization from incompatible pointer type
>   .get_vblank_counter = drm_vblank_count,
>   ^
> drivers/gpu/drm/msm/msm_drv.c:981:2: warning: (near initialization for 'msm_driver.get_vblank_counter')
> 
> Introduced by commit
> 
>   b90180b057f7 ("drm/irq: More pipe/crtc consistency cleanups")

Yes, that patch turned out to be incomplete. Daniel suggested to remove
it from drm-misc for now and I'll address this fully in a larger patch
for 4.4.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-14 12:51 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14  5:35 linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2015-08-14  5:35 ` Stephen Rothwell
2015-08-14 12:51 ` Thierry Reding [this message]
2015-08-14 12:51   ` Thierry Reding
  -- strict thread matches above, loose matches on Subject: below --
2025-12-16  0:56 Stephen Rothwell
2025-11-10  2:50 Stephen Rothwell
2025-11-10  2:24 Stephen Rothwell
2025-11-05  5:18 Stephen Rothwell
2025-06-18  5:13 Stephen Rothwell
2025-06-11  4:09 Stephen Rothwell
2025-08-01  4:34 ` Stephen Rothwell
2025-08-01 11:04   ` Dmitry Baryshkov
2025-01-06  6:46 Stephen Rothwell
2025-01-14  5:43 ` Stephen Rothwell
2025-01-14 11:40   ` Dmitry Baryshkov
2025-01-14 12:06     ` Stephen Rothwell
2024-12-20  4:42 Stephen Rothwell
2025-01-14  5:41 ` Stephen Rothwell
2025-01-16 10:34   ` Tomi Valkeinen
2025-01-16 11:50     ` Maxime Ripard
2024-10-10  5:09 Stephen Rothwell
2024-10-10  8:35 ` Thomas Hellström
2024-10-10  5:04 Stephen Rothwell
2024-08-01  6:03 Stephen Rothwell
2024-04-16  7:31 Stephen Rothwell
2024-04-16  8:25 ` Jocelyn Falempe
2024-03-26  5:12 Stephen Rothwell
2023-12-04  4:53 Stephen Rothwell
2023-12-04  4:53 ` Stephen Rothwell
2023-03-14  3:15 Stephen Rothwell
2023-03-14  3:15 ` Stephen Rothwell
2022-06-11  8:21 Stephen Rothwell
2022-06-11  8:21 ` Stephen Rothwell
2022-06-11 16:57 ` Doug Anderson
2022-06-11 16:57   ` Doug Anderson
2022-04-06  5:44 Stephen Rothwell
2022-04-06  5:44 ` Stephen Rothwell
2022-04-06  5:51 ` Stephen Rothwell
2022-04-06  5:51   ` Stephen Rothwell
2022-04-13  0:07 ` Stephen Rothwell
2022-04-13  0:07   ` Stephen Rothwell
2021-01-15  1:23 Stephen Rothwell
2021-01-15  1:23 ` Stephen Rothwell
2021-01-15 15:03 ` Nirmoy
2021-01-15 15:03   ` Nirmoy
2015-07-14  3:05 Stephen Rothwell
2015-07-14  3:05 ` Stephen Rothwell

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=20150814125119.GC22537@ulmo.nvidia.com \
    --to=treding@nvidia.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.