linux-kernel - linux-next: build failure after merge of the drm-panel 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-next>] [day] [month] [year] [list]

Message-ID: <20151124113816.3ed66bcc@canb.auug.org.au>
Date:	Tue, 24 Nov 2015 11:38:16 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Thierry Reding <thierry.reding@...il.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Werner Johansson <werner.johansson@...ymobile.com>,
	Bjorn Andersson <bjorn.andersson@...ymobile.com>
Subject: linux-next: build failure after merge of the drm-panel tree

Hi Thierry,

After merging the drm-panel tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/gpu/drm/panel/panel-panasonic-vvx10f034n00.c: In function 'wuxga_nt_panel_on':
drivers/gpu/drm/panel/panel-panasonic-vvx10f034n00.c:65:8: error: implicit declaration of function 'mipi_dsi_turn_on_peripheral' [-Werror=implicit-function-declaration]
  ret = mipi_dsi_turn_on_peripheral(dsi);
        ^
drivers/gpu/drm/panel/panel-panasonic-vvx10f034n00.c: In function 'wuxga_nt_panel_disable':
drivers/gpu/drm/panel/panel-panasonic-vvx10f034n00.c:79:2: error: implicit declaration of function 'mipi_dsi_shutdown_peripheral' [-Werror=implicit-function-declaration]
  mipi_dsi_shutdown_peripheral(wuxga_nt->dsi);
  ^

Caused by commit

  086ceb6b42ca ("drm/panel: Add Panasonic VVX10F034N00 MIPI DSI panel")

I have used the version of the drm-panel tree from next-20151123 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/