Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751474Ab2KJJLn (ORCPT ); Sat, 10 Nov 2012 04:11:43 -0500 Received: from moutng.kundenserver.de ([212.227.126.171]:57159 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750886Ab2KJJLi (ORCPT ); Sat, 10 Nov 2012 04:11:38 -0500 Date: Sat, 10 Nov 2012 10:11:21 +0100 From: Thierry Reding To: Stephen Warren Cc: Dave Airlie , linux-tegra@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: Re: [PATCH 1/2] drm: Add NVIDIA Tegra20 support Message-ID: <20121110091121.GA17319@avionic-0098.mockup.avionic-design.de> References: <1352469579-3337-1-git-send-email-thierry.reding@avionic-design.de> <1352469579-3337-2-git-send-email-thierry.reding@avionic-design.de> <509D9B4F.6060003@wwwdotorg.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <509D9B4F.6060003@wwwdotorg.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:WTAPvJFTEO9mw9Dv3PayhrrieKYMpjVmWAKN74yJBVk a/iryLoTOE3yolLfdbJF2YOf3f4h8UHAbBbJ/5Ix77KltKDlcE sUFinx6uiJlQ7xvX60JBZ/wQQoApjzGZR8WJTAfQ4Oowp6q5rh pPvQJDmc0Msz1bkjaU59Pel+PWgpF3ZONggkqYrfJrc9rJ1Uzw o+jJNUhmmhFriycvgwjF/a5JvT4C0th3zrkmPI0idcy944rMsR 5NouhpnYLGSBTVdQZbr10akXOXgXDZR4rr9blivI18sJqqeRJk m3lxQximzu7mt9sKSnyqjr6TRm2qHdUVODtui7B/Mwqpu5N4gf YAlwSq2yBGowtY+osb+hd+/KU0OnTRM8iUGidYOx1XTW3/FCdd QRhw9l3cvekrdHlio6LOq51BtNJ9G7gVPOvzIHbIlmqf+Rt2AZ 4BAiL Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3136 Lines: 72 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 09, 2012 at 05:09:51PM -0700, Stephen Warren wrote: > On 11/09/2012 06:59 AM, Thierry Reding wrote: > > This commit adds a KMS driver for the Tegra20 SoC. This includes basic > > support for host1x and the two display controllers found on the Tegra20 > > SoC. Each display controller can drive a separate RGB/LVDS output. >=20 > I applied these two patches and the two arch/arm/mach-tegra patches you > posted, directly on top of next-20121109, and I see the following build > failure: >=20 > > drivers/gpu/drm/tegra/output.c: In function 'tegra_output_init': > > drivers/gpu/drm/tegra/output.c:166:9: error: 'struct tegra_output' has = no member named 'display' > > drivers/gpu/drm/tegra/output.c:166:3: error: implicit declaration of fu= nction 'of_get_display' > > drivers/gpu/drm/tegra/output.c:167:20: error: 'struct tegra_output' has= no member named 'display' > > drivers/gpu/drm/tegra/output.c:168:25: error: 'struct tegra_output' has= no member named 'display' > > drivers/gpu/drm/tegra/output.c:179:13: error: 'struct tegra_output' has= no member named 'display' > > drivers/gpu/drm/tegra/output.c:180:3: error: implicit declaration of fu= nction 'display_put' > > drivers/gpu/drm/tegra/output.c:180:21: error: 'struct tegra_output' has= no member named 'display' > > drivers/gpu/drm/tegra/output.c:257:20: error: 'struct tegra_output' has= no member named 'display' > > drivers/gpu/drm/tegra/output.c: In function 'tegra_output_exit': > > drivers/gpu/drm/tegra/output.c:272:20: error: 'struct tegra_output' has= no member named 'display' >=20 > Does this depend on something not in linux-next? It looks like I missed some changes when I split the patches up and then forgot to check that the patches actually still build. I'll make sure to fix that in the next round. Sorry for the inconvenience. Thierry --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJQnho5AAoJEN0jrNd/PrOhRnwP/igeV7l4OF0hcJQbtwkSPsED pFfb5z9EqYz2xNH752ZAek4HLvfaIol6nrwlMoPWCORQ9hpeGCl1Lw8llIDl0dfW IMKe0/UMHwEOXQ4hllwADgQ99E88PZz3HeKLit4mxCiLlGAwWQtAeR0HUDAbidFt TVft5A9nk+aSJXoOQBRu+IarL7AIKwU6yVCAGk+nIsWFEbLJdcFyZEZYWyzrBYKc 6lrDqrSYx1t2ZGrgsJCzDdhxS+S8/B008o5AkSUWBsQBJWbRuApsQDDMcU/aYNG0 ijGis2l0BcBR0r3sMtnD7mEVRjoUwuPmjpxx8eiyHSKPCAqfVYluURF+Ikpl5px3 Td42u7joeKnx9JMK+ah0wVqomoT6Xezeeks2Er1U0epSvZuvFQUTPTubH5MPcqLt xcMDduFpNX0GfUyr4+h2BvmifQZbepeiraLvhf/ltmrXaKl62TNSRRLJL51ewdsa Dgdoyjt29uaWqFuJOFYmoeKDHaPSMDVmhIcIskdl7kWG3QrUHWX+K1JP9sEypr9r zFls0RKSPY6iZ80xSXoAHN31XAynzhjjpNPKSj2zlLPr297544cLTQa3AlyTvrSs 9hTs3f7uWGQV1Ng85vNsmy+Al8Qp2vuktaxwH1W7JajVj3Ub89yZ3fwCMAVXMbQe DAm0ojy+YljI6XfSmxLu =CbSM -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/