From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2.1/2] fixed up omap1 sparse irq support for v4.2
Date: Fri, 22 May 2015 16:36:24 +0200 [thread overview]
Message-ID: <39338069.RMptS8vVnc@wuerfel> (raw)
In-Reply-To: <20150521225938.GY10274@atomide.com>
On Thursday 21 May 2015 15:59:38 Tony Lindgren wrote:
> Here's this pull request updated for the randconfig errors found
> by Arnd.
>
> The following changes since commit 030bbdbf4c833bc69f502eae58498bc5572db736:
>
> Linux 4.1-rc3 (2015-05-10 15:12:29 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.2/omap1-v2
>
> for you to fetch changes up to 7bf15c4360b384e34d685616a77a8abf7dd8aea5:
>
> ARM: OMAP1: Fix section mismatch warnings for omap_cfg_reg (2015-05-21 14:50:23 -0700)
>
> ----------------------------------------------------------------
> 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.
Pulled into next/soc
> Note that this branch depends on a GPIO driver fix in v4.1-rc3
> d2d05c65c40e ("gpio: omap: Fix regression for MPUIO interrupts").
The branch is already based on 4.1-rc3, so we should be fine.
Thanks,
Arnd
prev parent reply other threads:[~2015-05-22 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 22:36 [GIT PULL 1/2] omap clean-up for v4.2 Tony Lindgren
2015-05-20 22:36 ` [GIT PULL 2/2] omap1 sparse irq support " Tony Lindgren
2015-05-21 22:59 ` [GIT PULL 2.1/2] fixed up " Tony Lindgren
2015-05-22 14:36 ` Arnd Bergmann [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=39338069.RMptS8vVnc@wuerfel \
--to=arnd@arndb.de \
--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