From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 2/2] omap1 sparse irq support for v4.2
Date: Thu, 21 May 2015 07:58:41 -0700 [thread overview]
Message-ID: <20150521145840.GQ10274@atomide.com> (raw)
In-Reply-To: <80194352.chs4cqVdmg@wuerfel>
* 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? What's the Kconfig option enabling
these errors?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
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 07:58:41 -0700 [thread overview]
Message-ID: <20150521145840.GQ10274@atomide.com> (raw)
In-Reply-To: <80194352.chs4cqVdmg@wuerfel>
* 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? What's the Kconfig option enabling
these errors?
Regards,
Tony
next prev parent reply other threads:[~2015-05-21 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 12:11 [GIT PULL 2/2] omap1 sparse irq support for v4.2 Arnd Bergmann
2015-05-21 14:58 ` Tony Lindgren [this message]
2015-05-21 14:58 ` Tony Lindgren
2015-05-21 15:40 ` Arnd Bergmann
2015-05-21 15:40 ` Arnd Bergmann
2015-05-21 15:49 ` Tony Lindgren
2015-05-21 15:49 ` Tony Lindgren
2015-05-21 16:54 ` Tony Lindgren
2015-05-21 16:54 ` Tony Lindgren
2015-05-21 18:36 ` Tony Lindgren
2015-05-21 18:36 ` Tony Lindgren
2015-05-21 21:33 ` Arnd Bergmann
2015-05-21 21:33 ` Arnd Bergmann
2015-05-21 21:47 ` Tony Lindgren
2015-05-21 21:47 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2015-05-21 12:14 Arnd Bergmann
2015-05-21 12:47 ` Arnd Bergmann
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
2015-05-20 22:36 ` Tony Lindgren
2015-05-20 22:36 ` 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=20150521145840.GQ10274@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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.