From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 1/2] omap device tree changes for v3.15, part 3
Date: Mon, 17 Mar 2014 15:14:06 +0100 [thread overview]
Message-ID: <201403171514.07194.arnd@arndb.de> (raw)
In-Reply-To: <20140313200135.GA5981@atomide.com>
On Thursday 13 March 2014, Tony Lindgren wrote:
> Hi,
>
> Resending these two, looks like my updated scripts have some issues hitting
> the mailing lists..
>
> The following changes since commit 18c49af3ee9e32a535413a949672bea726699f04:
>
> ARM: dts: am335x-evmsk: enable dual_emac mode (2014-03-05 11:53:36 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.15/dt-part3
>
> for you to fetch changes up to e1902bbe44844597a38c8cbae30ca895f6e126ee:
>
> ARM: dts: Add MMC2/SDIO/WLAN support for cm-t3530 (2014-03-12 10:40:37 -0700)
>
> ----------------------------------------------------------------
> Device tree related changes to the omap iommu driver as that
> is finally getting updated. Also few trivial board related
> .dts updates to add more devices.
Pulled into next/dt, thanks!
I haven't really been following the iommu discussions, so I have to trust
you are doing the right thing here. What is the status on iommu
support through DT? Do we have or require a generic binding for iommus?
Are you following that, or will you have to do incompatible changes to
do that?
Arnd
next prev parent reply other threads:[~2014-03-17 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 20:01 [GIT PULL 1/2] omap device tree changes for v3.15, part 3 Tony Lindgren
2014-03-13 20:02 ` [GIT PULL 2/2] omap overo related device tree changes for v3.15 Tony Lindgren
2014-03-17 14:18 ` Arnd Bergmann
2014-03-17 16:50 ` Tony Lindgren
2014-03-17 14:14 ` Arnd Bergmann [this message]
2014-03-17 16:45 ` [GIT PULL 1/2] omap device tree changes for v3.15, part 3 Tony Lindgren
2014-03-17 20:55 ` Suman Anna
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=201403171514.07194.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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