linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Anholt <eric@anholt.net>
Cc: Dave Airlie <airlied@linux.ie>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tom Cooksey <tom.cooksey@arm.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Fri, 2 Jun 2017 13:59:25 +1000	[thread overview]
Message-ID: <20170602135925.70272f31@canb.auug.org.au> (raw)
In-Reply-To: <20170525114933.1e1dea04@canb.auug.org.au>

Hi all,

On Thu, 25 May 2017 11:49:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt <eric@anholt.net> wrote:
> >
> > Stephen Rothwell <sfr@canb.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

  reply	other threads:[~2017-06-02  3:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  2:07 linux-next: build warnings after merge of the drm tree Stephen Rothwell
2017-05-19 17:49 ` Eric Anholt
2017-05-25  1:49   ` Stephen Rothwell
2017-06-02  3:59     ` Stephen Rothwell [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-11-01  3:16 Stephen Rothwell
2017-11-01  9:58 ` Boris Brezillon
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=20170602135925.70272f31@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eric@anholt.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tom.cooksey@arm.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;
as well as URLs for NNTP newsgroup(s).