From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 2/2] omap1 sparse irq support for v4.2
Date: Thu, 21 May 2015 08:49:57 -0700 [thread overview]
Message-ID: <20150521154957.GR10274@atomide.com> (raw)
In-Reply-To: <2613552.WPU8qB3AF6@wuerfel>
* Arnd Bergmann <arnd@arndb•de> [150521 08:41]:
> On Thursday 21 May 2015 07:58:41 Tony Lindgren wrote:
> > * Arnd Bergmann <arnd@arndb•de> [150521 05:13]:
> > > On Wednesday 20 May 2015 15:36:05 Tony Lindgren wrote:
> > > > Add support for CONFIG_SPARSE_IRQ for omap1. This takes us a bit closer
> > > > to making omap1 support multiarch. After this series we still need to
> > > > make omap1 use the common clock framework and fix up the drivers to not
> > > > rely on includes from mach and plat directories.
> > > >
> > > > Note that this branch depends on a GPIO driver fix in v4.1-rc3
> > > > d2d05c65c40e ("gpio: omap: Fix regression for MPUIO interrupts").
> > > >
> > >
> > > I'm getting lots of build errors in linux-next, which I think are
> > > caused by this series.
> >
> > Hmm is this with make randconfig?
>
> Yes, all sorts of randconfig builds hit different parts here
>
> > What's the Kconfig option enabling these errors?
>
> From what I can tell, this is simply a result of enabling
> CONFIG_SPARSE_IRQ, which results in linux/irq.h no longer
> implicitly including mach/hardware.h through mach/irqs.h.
Hmm not seeing that here, well at least not with what I've
tried so far.
> You should be able to see these errors by just enabling
> the respective drivers. The errors manifest as a long list
> of undefined symbols like
>
> /git/arm-soc/arch/arm/mach-omap1/io.c:33:28: error: 'OMAP1_IO_OFFSET' undeclared here (not in a function)
> /git/arm-soc/arch/arm/mach-omap1/io.c:43:14: error: 'OMAP7XX_DSP_BASE' undeclared here (not in a function)
> /git/arm-soc/arch/arm/mach-omap1/serial.c:114:33: note: each undeclared identifier is reported only once for each function it appears in
> /git/arm-soc/arch/arm/mach-omap1/pm.c:217:23: error: 'ULPD_SOFT_DISABLE_REQ_REG' undeclared (first use in this function)
> /git/arm-soc/drivers/video/fbdev/omap/sossi.c:608:17: error: 'MOD_CONF_CTRL_1' undeclared (first use in this function)
>
> Then again, it is possible that I only see the errors because of
> an interaction with another patch from my randconfig fixes
> series.
I think there's something like that going on.. Maybe you're
now enabling multiarch for omap1 in your branch?
Regards,
Tony
next prev parent reply other threads:[~2015-05-21 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <80194352.chs4cqVdmg@wuerfel>
2015-05-21 14:58 ` [GIT PULL 2/2] omap1 sparse irq support for v4.2 Tony Lindgren
2015-05-21 15:40 ` Arnd Bergmann
2015-05-21 15:49 ` Tony Lindgren [this message]
2015-05-21 16:54 ` Tony Lindgren
2015-05-21 18:36 ` Tony Lindgren
2015-05-21 21:33 ` Arnd Bergmann
2015-05-21 21:47 ` Tony Lindgren
[not found] <4094934.StqYY08vL5@wuerfel>
2015-05-21 12:47 ` Arnd Bergmann
2015-05-20 22:36 [GIT PULL 1/2] omap clean-up " Tony Lindgren
2015-05-20 22:36 ` [GIT PULL 2/2] omap1 sparse irq support " Tony Lindgren
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=20150521154957.GR10274@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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