linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] mxs sparse-irq support
Date: Tue, 11 Sep 2012 15:54:57 +0800	[thread overview]
Message-ID: <1347350100-4674-3-git-send-email-shawn.guo@linaro.org> (raw)
In-Reply-To: <1347350100-4674-1-git-send-email-shawn.guo@linaro.org>

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.

----------------------------------------------------------------
Shawn Guo (6):
      gpio/mxs: adopt irq_domain support for mxs gpio driver
      ARM: mxs: retrieve timer irq from device tree
      ARM: mxs: select MULTI_IRQ_HANDLER
      ARM: mxs: adopt irq_domain support for icoll driver
      ARM: mxs: select SPARSE_IRQ
      ARM: mxs: remove mach/irqs.h

 arch/arm/Kconfig                             |    2 ^[[32m+^[[m
 arch/arm/boot/dts/imx23.dtsi                 |    5 ^[[32m+^[[m^[[31m-^[[m
 arch/arm/boot/dts/imx28.dtsi                 |    5 ^[[32m+^[[m^[[31m-^[[m
 arch/arm/mach-mxs/icoll.c                    |   63 ^[[32m++++++++++++++++++++++^[[m^[[31m----^[[m
 arch/arm/mach-mxs/include/mach/common.h      |    3 ^[[32m+^[[m^[[31m-^[[m
 arch/arm/mach-mxs/include/mach/entry-macro.S |   35 ^[[31m--------------^[[m
 arch/arm/mach-mxs/include/mach/irqs.h        |   32 ^[[31m-------------^[[m
 arch/arm/mach-mxs/mach-mxs.c                 |   39 ^[[32m++^[[m^[[31m--------------^[[m
 arch/arm/mach-mxs/timer.c                    |   13 ^[[32m+++++^[[m^[[31m-^[[m
 drivers/clk/mxs/clk-imx23.c                  |    2 ^[[32m+^[[m^[[31m-^[[m
 drivers/clk/mxs/clk-imx28.c                  |    2 ^[[32m+^[[m^[[31m-^[[m
 drivers/gpio/gpio-mxs.c                      |   48 ^[[32m++++++++++++^[[m^[[31m--------^[[m
 12 files changed, 112 insertions(+), 137 deletions(-)
 delete mode 100644 arch/arm/mach-mxs/include/mach/entry-macro.S
 delete mode 100644 arch/arm/mach-mxs/include/mach/irqs.h

  parent reply	other threads:[~2012-09-11  7:54 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 ` Shawn Guo [this message]
2012-09-13  5:56   ` [GIT PULL 2/4] mxs sparse-irq support Olof Johansson
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=1347350100-4674-3-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo@linaro.org \
    --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;
as well as URLs for NNTP newsgroup(s).