All of lore.kernel.org
 help / color / mirror / Atom feed
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next ARM multi-platform randconfig errors
Date: Fri, 19 Apr 2013 22:53:50 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.00.1304192249250.24986@utopia.booyaka.com> (raw)
In-Reply-To: <201304200008.28716.arnd@arndb.de>

Hi,

On Sat, 20 Apr 2013, Arnd Bergmann wrote:

> I think part of the problem is the way the Makefile is laid
> out, e.g.
> 
> clockdomain-common                      += clockdomain.o
> obj-$(CONFIG_ARCH_OMAP2)                += $(clockdomain-common)
> obj-$(CONFIG_ARCH_OMAP3)                += $(clockdomain-common)
> obj-$(CONFIG_ARCH_OMAP4)                += $(clockdomain-common)
> obj-$(CONFIG_SOC_AM33XX)                += $(clockdomain-common)
> obj-$(CONFIG_SOC_OMAP5)                 += $(clockdomain-common)
> 
> This results in building clockdomain.o whenever any of the various
> SoCs are enabled, but not when none of them are enabled.
> 
> However, according to the error messages, this driver is actually
> referenced by code that is enabled unconditionally.

Seems to me that's where the issue is: in the code that uses it, like 
omap_hwmod.o.  If we're not building code for any OMAP SoCs, it seems 
rather pointless to build omap_hwmod.o -- at least until omap_hwmod.o is 
moved out into drivers/.


- Paul

  reply	other threads:[~2013-04-19 22:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  3:06 linux-next ARM multi-platform randconfig errors Rob Herring
2013-04-19 16:12 ` Tony Lindgren
2013-04-19 16:41   ` Tomi Valkeinen
2013-04-19 19:43     ` Tony Lindgren
2013-04-19 19:51       ` Tony Lindgren
2013-04-19 20:11       ` Arnd Bergmann
2013-04-19 20:40         ` Tony Lindgren
2013-04-19 20:58           ` Arnd Bergmann
     [not found]             ` <20130419215134.GY10155@atomide.com>
2013-04-19 22:08               ` Arnd Bergmann
2013-04-19 22:53                 ` Paul Walmsley [this message]
2013-04-19 21:02           ` Tony Lindgren
2013-04-19 21:09           ` Tony Lindgren
2013-04-19 19:52     ` Jon Hunter
2013-04-19 20:42       ` Tony Lindgren
2013-04-19 17:23   ` Tony Lindgren
2013-04-22  7:23   ` Roger Quadros
2013-04-22  8:21     ` Felipe Balbi
2013-04-22 11:52       ` Felipe Balbi
2013-04-22 12:45         ` Kishon Vijay Abraham I
2013-04-22 13:04           ` Felipe Balbi
2013-04-22 17:32 ` Mikulas Patocka
2013-04-22 22:57   ` Rob Herring
2013-05-13 22:37     ` [PATCH] bcache: Fix link errors on ARM Mikulas Patocka
2013-05-13 22:37       ` Mikulas Patocka
2013-04-22 18:59 ` linux-next ARM multi-platform randconfig errors Mike Turquette

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=alpine.DEB.2.00.1304192249250.24986@utopia.booyaka.com \
    --to=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.