From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] mxs sparse-irq support
Date: Wed, 12 Sep 2012 22:56:47 -0700 [thread overview]
Message-ID: <20120913055647.GF24290@quad.lixom.net> (raw)
In-Reply-To: <1347350100-4674-3-git-send-email-shawn.guo@linaro.org>
On Tue, Sep 11, 2012 at 03:54:57PM +0800, Shawn Guo wrote:
> The following changes since commit d9875690d9b89a866022ff49e3fcea892345ad92:
>
> Linux 3.6-rc2 (2012-08-16 14:51:24 -0700)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/shawnguo/linux-2.6.git tags/mxs-sparse-irq
>
> for you to fetch changes up to 6608f13fabdb1f9ecbd502763ba33ca2646834c8:
>
> ARM: mxs: remove mach/irqs.h (2012-09-03 09:32:17 +0800)
>
> ----------------------------------------------------------------
> mxs-sparse-irq
>
> The series adds irqdomain support for mach-mxs and then enables
> sparse-irq. It dependes on pull request mxs-dt-3.7.
Thanks, pulled in under next/soc2 due to the dt dependency.
However, for the future: if you're truly dependent on the dt branch to
build/boot, you should use that as a base for this branch. Otherwise you
can end up in a state with git bisect where you only have this branch
applied but not the other one.
-Olof
next prev parent reply other threads:[~2012-09-13 5:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 7:54 [GIT PULL 0/4] mxs changes for 3.7 Shawn Guo
2012-09-11 7:54 ` [GIT PULL 1/4] mxs device tree " Shawn Guo
2012-09-13 5:48 ` Olof Johansson
2012-09-11 7:54 ` [GIT PULL 2/4] mxs sparse-irq support Shawn Guo
2012-09-13 5:56 ` Olof Johansson [this message]
2012-09-13 6:16 ` Shawn Guo
2012-09-13 7:42 ` Olof Johansson
2012-09-11 7:54 ` [GIT PULL 3/4] mxs clk device tree lookup Shawn Guo
2012-09-11 8:58 ` Shawn Guo
2012-09-13 6:08 ` Olof Johansson
2012-09-13 17:23 ` Turquette, Mike
2012-09-11 7:54 ` [GIT PULL 4/4] mxs defconfig update for 3.7 Shawn Guo
2012-09-13 6:10 ` Olof Johansson
2012-09-13 6:17 ` Shawn Guo
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=20120913055647.GF24290@quad.lixom.net \
--to=olof@lixom.net \
--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.