From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"James Qian Wang (Arm Technology China)"
<james.qian.wang@arm.com>
Subject: linux-next: build warning after merge of the mali-dp tree
Date: Fri, 18 Jan 2019 11:28:11 +1100 [thread overview]
Message-ID: <20190118112811.091dd962@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
Hi Liviu,
After merging the mali-dp tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/gpu/drm/arm/display/komeda/komeda_dev.c: In function 'komeda_parse_dt':
drivers/gpu/drm/arm/display/komeda/komeda_dev.c:52:26: warning: unused variable 'pdev' [-Wunused-variable]
struct platform_device *pdev = to_platform_device(dev);
^~~~
Introduced by commit
7e8d4fcf8daf ("drm: arm/komeda: Remove IRQ parsing from initial series")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-01-18 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 0:28 Stephen Rothwell [this message]
2019-01-18 10:43 ` linux-next: build warning after merge of the mali-dp tree Liviu Dudau
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=20190118112811.091dd962@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Liviu.Dudau@arm.com \
--cc=james.qian.wang@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).