From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build warning after merge of the drm tree
Date: Thu, 4 May 2017 08:33:36 +1000 [thread overview]
Message-ID: <20170504083336.35ed36ee@canb.auug.org.au> (raw)
Hi all,
Sorry that I did not notice this at the time ... This is now in Linus'
tree.
After merging the drm tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
arch/arm/configs/multi_v7_defconfig:596:warning: symbol value 'm' invalid for ROCKCHIP_ANALOGIX_DP
arch/arm/configs/multi_v7_defconfig:597:warning: symbol value 'm' invalid for ROCKCHIP_DW_HDMI
arch/arm/configs/multi_v7_defconfig:598:warning: symbol value 'm' invalid for ROCKCHIP_DW_MIPI_DSI
arch/arm/configs/multi_v7_defconfig:599:warning: symbol value 'm' invalid for ROCKCHIP_INNO_HDMI
Introduced by commit
8820b68bd378 ("drm/rockchip: Refactor the component match logic.")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-05-03 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 22:33 Stephen Rothwell [this message]
[not found] ` <tencent_62AF37B85899E2EA593CCE3B@qq.com>
2017-05-04 1:42 ` linux-next: build warning after merge of the drm tree 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=20170504083336.35ed36ee@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.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