linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: treding@nvidia.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: Latest build test randconfig errors
Date: Thu, 16 Oct 2014 15:40:30 +0200	[thread overview]
Message-ID: <20141016134029.GA27411@ulmo.nvidia.com> (raw)
In-Reply-To: <20141016083120.GN27405@n2100.arm.linux.org.uk>

On Thu, Oct 16, 2014 at 09:31:20AM +0100, Russell King - ARM Linux wrote:
> The cause seems to be a missing dependency between the Tegra DRM
> code and COMMON_CLK, caused by:
> 
> commit 158b50aefa14ba18ee94b691f83a7e5d30539433
> Author: Thierry Reding <treding@nvidia.com>
> Date:   Wed Nov 20 20:39:35 2013 +0100
> 
>     drm/tegra: Increase compile test coverage
> 
> ARCH_MULTIPLATFORM would have selected COMMON_CLK, and ARCH_TEGRA
> requires ARCH_MULTIPLATFORM to be set so that part was redundant
> in the original dependencies:
> 
> menuconfig ARCH_TEGRA
>         bool "NVIDIA Tegra" if ARCH_MULTI_V7

I've queued the following fix for this. As I understand that should fix
this particular issue.

diff --git a/drivers/gpu/drm/tegra/Kconfig b/drivers/gpu/drm/tegra/Kconfig
index 354ddb29231f..74d9d621453d 100644
--- a/drivers/gpu/drm/tegra/Kconfig
+++ b/drivers/gpu/drm/tegra/Kconfig
@@ -1,6 +1,7 @@
 config DRM_TEGRA
 	tristate "NVIDIA Tegra DRM"
 	depends on ARCH_TEGRA || (ARM && COMPILE_TEST)
+	depends on COMMON_CLK
 	depends on DRM
 	depends on RESET_CONTROLLER
 	select DRM_KMS_HELPER

Thanks,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141016/8dd80525/attachment.sig>

      reply	other threads:[~2014-10-16 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  8:31 Latest build test randconfig errors Russell King - ARM Linux
2014-10-16 13:40 ` Thierry Reding [this message]

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=20141016134029.GA27411@ulmo.nvidia.com \
    --to=treding@nvidia.com \
    --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;
as well as URLs for NNTP newsgroup(s).