All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 21 Jan 2015 16:57:48 -0800	[thread overview]
Message-ID: <20150122005748.GF29014@quad.lixom.net> (raw)
In-Reply-To: <54b99dd4.c1ef440a.27a8.ffffc87fSMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, Jan 16, 2015 at 03:21:22PM -0800, Tony Lindgren wrote:
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> 
>   Linux 3.19-rc1 (2014-12-20 17:08:50 -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-pt1
> 
> for you to fetch changes up to 7300bfff886a1340cfeb252035303e265cd556d9:
> 
>   ARM: dts: omap3-gta04: Add handling for tv output (2015-01-13 08:02:21 -0800)
> 
> ----------------------------------------------------------------
> Device tree changes for omaps. Mostly to add support for new
> am437x-idk and update am437x-sk boards. Also enabling new
> devices for multiple boards.

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
Date: Wed, 21 Jan 2015 16:57:48 -0800	[thread overview]
Message-ID: <20150122005748.GF29014@quad.lixom.net> (raw)
In-Reply-To: <54b99dd4.c1ef440a.27a8.ffffc87fSMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, Jan 16, 2015 at 03:21:22PM -0800, Tony Lindgren wrote:
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> 
>   Linux 3.19-rc1 (2014-12-20 17:08:50 -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-pt1
> 
> for you to fetch changes up to 7300bfff886a1340cfeb252035303e265cd556d9:
> 
>   ARM: dts: omap3-gta04: Add handling for tv output (2015-01-13 08:02:21 -0800)
> 
> ----------------------------------------------------------------
> Device tree changes for omaps. Mostly to add support for new
> am437x-idk and update am437x-sk boards. Also enabling new
> devices for multiple boards.

Merged, thanks.


-Olof

  parent reply	other threads:[~2015-01-22  0:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 23:21 [GIT PULL 1/3] omap non-urgent fixes for v3.20 Tony Lindgren
2015-01-16 23:21 ` [GIT PULL 2/3] omap clean-up " Tony Lindgren
2015-01-16 23:21 ` Tony Lindgren
2015-01-16 23:21 ` Tony Lindgren
2015-01-16 23:21 ` [GIT PULL 3/3] omap device tree changes " Tony Lindgren
2015-01-16 23:21 ` Tony Lindgren
2015-01-16 23:21 ` Tony Lindgren
     [not found] ` <54b99dd2.d0bc420a.57d0.ffffc9f5SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22  0:50   ` [GIT PULL 2/3] omap clean-up " Olof Johansson
2015-01-22  0:50     ` Olof Johansson
     [not found] ` <54b99dd4.c1ef440a.27a8.ffffc87fSMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22  0:57   ` Olof Johansson [this message]
2015-01-22  0:57     ` [GIT PULL 3/3] omap device tree changes " 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=20150122005748.GF29014@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.