From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 3/3] omap device tree changes for v3.20, part 2
Date: Fri, 23 Jan 2015 13:49:25 -0800 [thread overview]
Message-ID: <20150123214925.GC20896@quad.lixom.net> (raw)
In-Reply-To: <54be9e8f.6a58460a.68af.68c1SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Jan 20, 2015 at 10:25:40AM -0800, Tony Lindgren wrote:
> The following changes since commit 7300bfff886a1340cfeb252035303e265cd556d9:
>
> ARM: dts: omap3-gta04: Add handling for tv output (2015-01-13 08:02:21 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/dt-pt2
>
> for you to fetch changes up to 1f43c45df7afb706470f7d81d983dd7763a9452f:
>
> ARM: dts: dra72-evm: Add qspi device (2015-01-20 10:07:25 -0800)
>
> ----------------------------------------------------------------
> More changes for omap dts files mostly to add support for
> dm816x devices and clocks. Also adds a qspi device for
> dra72x-evm.
>
Merged, thanks.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] omap device tree changes for v3.20, part 2
Date: Fri, 23 Jan 2015 13:49:25 -0800 [thread overview]
Message-ID: <20150123214925.GC20896@quad.lixom.net> (raw)
In-Reply-To: <54be9e8f.6a58460a.68af.68c1SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Jan 20, 2015 at 10:25:40AM -0800, Tony Lindgren wrote:
> The following changes since commit 7300bfff886a1340cfeb252035303e265cd556d9:
>
> ARM: dts: omap3-gta04: Add handling for tv output (2015-01-13 08:02:21 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/dt-pt2
>
> for you to fetch changes up to 1f43c45df7afb706470f7d81d983dd7763a9452f:
>
> ARM: dts: dra72-evm: Add qspi device (2015-01-20 10:07:25 -0800)
>
> ----------------------------------------------------------------
> More changes for omap dts files mostly to add support for
> dm816x devices and clocks. Also adds a qspi device for
> dra72x-evm.
>
Merged, thanks.
-Olof
next prev parent reply other threads:[~2015-01-23 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 18:25 [GIT PULL 1/3] drop legacy booting for omap3517 Tony Lindgren
2015-01-20 18:25 ` [GIT PULL 2/3] omap defconfig changes for v3.20 Tony Lindgren
2015-01-20 18:25 ` Tony Lindgren
2015-01-20 18:25 ` Tony Lindgren
2015-01-20 18:25 ` [GIT PULL 3/3] omap device tree changes for v3.20, part 2 Tony Lindgren
2015-01-20 18:25 ` Tony Lindgren
2015-01-20 18:25 ` Tony Lindgren
[not found] ` <54be9e8c.6a58460a.68af.68a6SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-23 21:47 ` [GIT PULL 2/3] omap defconfig changes for v3.20 Olof Johansson
2015-01-23 21:47 ` Olof Johansson
2015-01-23 21:50 ` Tony Lindgren
2015-01-23 21:50 ` Tony Lindgren
[not found] ` <54be9e8f.6a58460a.68af.68c1SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-23 21:49 ` Olof Johansson [this message]
2015-01-23 21:49 ` [GIT PULL 3/3] omap device tree changes for v3.20, part 2 Olof Johansson
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=20150123214925.GC20896@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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 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.