linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Olof Johansson <olof@lixom.net>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 4/5] First round of DT related omap changes
Date: Wed, 29 Feb 2012 21:08:29 +0000	[thread overview]
Message-ID: <201202292108.29906.arnd@arndb.de> (raw)
In-Reply-To: <0Luuob-1STTV50YM5-00zayn@mx.kundenserver.de>

On Wednesday 29 February 2012, Tony Lindgren wrote:
> Benoit Cousson (10):
>       arm/dts: OMAP: Remove bootargs node from board files
>       ARM: OMAP2+: kconfig: Enable devicetree by default for OMAP2+ systems
>       ARM: OMAP2+: board-generic: Remove un-needed .atag_offset for DT_MACHINE
>       ARM: OMAP2+: omap_device: Replace dev_warn by dev_dbg in omap_device_build_from_dt
>       ARM: OMAP2+: pm: Do not init statically the SR and voltage layer with DT
>       ARM: OMAP1: kconfig: Enable IRQ_DOMAIN by default for OMAP1 platforms
>       arm/dts: OMAP3&4: Remove the '0x' prefix for serial nodes
>       arm/dts: OMAP4: Add i2c controller nodes
>       arm/dts: OMAP3: Add i2c controller nodes
>       arm/dts: OMAP4: Update DTS file with new GIC bindings
> 
> Tony Lindgren (3):
>       Merge branch 'for_3.4/dt_base' of git://git.kernel.org/.../bcousson/linux-omap-dt into dt
>       ARM: OMAP2+: Set Kconfig dependencies for PROC_DEVICETREE
>       Merge branch 'for_3.4/dts_updates' of git://git.kernel.org/.../bcousson/linux-omap-dt into dt
> 
> Vaibhav Hiremath (1):
>       arm/dts: Add support for TI OMAP3 EVM board

Pulled into next/dt. Thanks,

	Arnd

       reply	other threads:[~2012-02-29 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0Luuob-1STTV50YM5-00zayn@mx.kundenserver.de>
2012-02-29 21:08 ` Arnd Bergmann [this message]
     [not found] <pull-1330546506-268554>
2012-02-29 20:15 ` [GIT PULL 4/5] First round of DT related omap changes 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=201202292108.29906.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tony@atomide.com \
    /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).