linux-kernel - Re: linux-next: build warnings after merge of the drm tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170602135925.70272f31@canb.auug.org.au>
Date:   Fri, 2 Jun 2017 13:59:25 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Eric Anholt <eric@...olt.net>
Cc:     Dave Airlie <airlied@...ux.ie>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Tom Cooksey <tom.cooksey@....com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Linus Walleij <linus.walleij@...aro.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: linux-next: build warnings after merge of the drm tree

Hi all,

On Thu, 25 May 2017 11:49:42 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt <eric@...olt.net> wrote:
> >
> > Stephen Rothwell <sfr@...b.auug.org.au> writes:
> >   
> > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > > produced these warnings:
> > >
> > > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init' defined but not used [-Wunused-function]
> > >  static int pl111_modeset_init(struct drm_device *dev)
> > >             ^
> > > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined but not used [-Wunused-variable]
> > >  static struct drm_driver pl111_drm_driver = {
> > >                           ^    
> > 
> > Sorry about that -- I thought that kbuild test robot would give me
> > notification of new warnings.
> > 
> > Patch incoming.  
> 
> I saw the patch, but it doesn't seem to have been applied anywhere yet.

So these warnings went away yesterday, but are back today after quite a
few patches were dropped from the drm-misc tree.

Yesterday it contained theses (relative to the drm tree):

9a8d5e4a53dc drm/vc4: Fix comment in vc4_drv.h
66d6dd45eee2 drm/pl111: fix warnings without CONFIG_ARM_AMBA
91110a4b64fe drm/atomic: Consitfy mode parameter to drm_atomic_set_mode_for_crtc()
fb51cbfd4b2e drm/arcgpu: Drop drm_vblank_cleanup
e3ec0e1e38a5 drm/atmel: Drop drm_vblank_cleanup
85769cf7cd7f drm/imx: Drop drm_vblank_cleanup
a360b39b5137 drm/meson: Drop drm_vblank_cleanup
25b905fe4323 drm/stm: Drop drm_vblank_cleanup
d79373bd4d7e drm/sun4i: Drop drm_vblank_cleanup
8938d13585bc drm: better document how to send out the crtc disable event
46466b0dac3f drm: Use vsnprintf extension %ph
99cdb35e787b drm/doc: move printf helpers out of drmP.h
e7cc23de3e4e drm/pl111: select DRM_PANEL
7dbcbce9f551 drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback
faf94a0883ce drm: Use mode_valid() in atomic modeset
97f973d65260 drm: Use new mode_valid() helpers in connector probe helper
b1240f81a186 drm: Introduce drm_bridge_mode_valid()
da251bf8f935 drm: Add drm_{crtc/encoder/connector}_mode_valid()
18e51064c42c drm: Remove drm_device->virtdev
a301b1118615 drm: todo: remove task about switch to drm_connector_list_iter
eb53a46be597 drm: remove unsafe drm_for_each_connector()
4894bf711d19 drm/vc4: use drm_for_each_connector_iter()
875dd62697fe drm/nouveau: use drm_for_each_connector_iter()
c8bf8b968adb drm/mediatek: use drm_for_each_connector_iter()
2fd96b4116bf drm/i915: use drm_for_each_connector_iter()
2cbeb64f6c70 drm/rockchip: use drm_for_each_connector_iter()
48a92916729b drm/exynos: use drm_for_each_connector_iter()

Today it only has:

2d7b56378d32 drm/rockchip: gem: add the lacks lock and trivial changes

-- 
Cheers,
Stephen Rothwell