public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] part 2 of omap intc changes for v3.18 merge window
Date: Thu, 25 Sep 2014 23:58:32 +0200	[thread overview]
Message-ID: <201409252358.33038.arnd@arndb.de> (raw)
In-Reply-To: <pull-1411070912-460910>

On Thursday 18 September 2014, Tony Lindgren wrote:
> The following changes since commit 55601c9f24670ba926ebdd4d712ac3b177232330:
> 
>   arm: omap: intc: switch over to linear irq domain (2014-09-11 13:05:50 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/intc-part2-for-v3.18
> 
> for you to fetch changes up to 64d5947b9ee1284b38b8e212e7c94024452b2bb4:
> 
>   irqchip: omap-intc: remove unnecessary comments (2014-09-16 14:45:01 -0700)
> 
> ----------------------------------------------------------------
> Second part of omap intc interrupt controller changes to
> move it to drivers.
> 
> ----------------------------------------------------------------
> Felipe Balbi (10):
>       arm: omap2: n8x0: move i2c devices to DT
>       irqchip: add irq-omap-intc.h header
>       arm: omap: irq: move irq.c to drivers/irqchip/
>       irqchip: omap-intc: minor improvement to omap_irq_pending()
>       irqchip: omap-intc: comment style cleanup
>       irqchip: omap-intc: remove unnecesary of_address_to_resource() call
>       irqchip: omap-intc: enable IP protection
>       irqchip: omap-intc: enable TURBO idle mode
>       irqchip: omap-intc: correct maximum number or MIR registers
>       irqchip: omap-intc: remove unnecessary comments
> 
>  arch/arm/boot/dts/omap2420-n810.dts                |  7 +++
>  arch/arm/boot/dts/omap2420-n8x0-common.dtsi        |  6 ++
>  arch/arm/mach-omap2/Kconfig                        |  1 +
>  arch/arm/mach-omap2/Makefile                       |  3 +-
>  arch/arm/mach-omap2/board-n8x0.c                   | 26 +--------
>  arch/arm/mach-omap2/common-board-devices.h         |  5 ++
>  arch/arm/mach-omap2/common.h                       | 10 +---
>  arch/arm/mach-omap2/pdata-quirks.c                 |  2 +
>  drivers/irqchip/Kconfig                            |  5 ++
>  drivers/irqchip/Makefile                           |  1 +
>  .../irq.c => drivers/irqchip/irq-omap-intc.c       | 64 +++++++++++++---------
>  include/linux/irqchip/irq-omap-intc.h              | 32 +++++++++++
>  12 files changed, 101 insertions(+), 61 deletions(-)
>  rename arch/arm/mach-omap2/irq.c => drivers/irqchip/irq-omap-intc.c (89%)
>  create mode 100644 include/linux/irqchip/irq-omap-intc.h
> 

Pulled into next/drivers, thanks!

	Arnd

      parent reply	other threads:[~2014-09-25 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 20:11 [GIT PULL 1/4] part 2 of omap intc changes for v3.18 merge window Tony Lindgren
2014-09-18 20:11 ` [GIT PULL 2/4] part 2 of omap SoC " Tony Lindgren
2014-09-25 22:07   ` Arnd Bergmann
2014-09-18 20:11 ` [GIT PULL 3/4] part 2 of omap dts " Tony Lindgren
2014-09-25 22:08   ` Arnd Bergmann
2014-09-18 20:11 ` [GIT PULL 4/4] omap clean-up " Tony Lindgren
2014-09-25 22:10   ` Arnd Bergmann
2014-09-25 21:58 ` 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=201409252358.33038.arnd@arndb.de \
    --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