From: Eric Anholt <eric@anholt.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Dave Airlie <airlied@linux.ie>
Cc: 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>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Fri, 19 May 2017 10:49:06 -0700 [thread overview]
Message-ID: <87y3tsg2jx.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20170519120729.597f5a9e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi Dave,
>
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-19 17:49 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 [this message]
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
-- 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=87y3tsg2jx.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).