linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/6] omap display and board pdata changes for v3.13 merge window
Date: Mon, 14 Oct 2013 15:48:54 -0700	[thread overview]
Message-ID: <871u3n4gfd.fsf@linaro.org> (raw)
In-Reply-To: <5258a9a9.0325310a.6fb0.ffffa1b2SMTPIN_ADDED_MISSING@mx.google.com> (Tony Lindgren's message of "Fri, 11 Oct 2013 18:44:59 -0700")

Tony Lindgren <tony@atomide.com> writes:

> The following changes since commit d0e639c9e06d44e713170031fe05fb60ebe680af:
>
>   Linux 3.12-rc4 (2013-10-06 14:00:20 -0700)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/board-signed
>
> for you to fetch changes up to 9e490f486ea9ce7644be913e03ee5ccdf1be20f7:
>
>   Merge branch 'omap-for-v3.13/n900' into omap-for-v3.13/board (2013-10-11 16:14:23 -0700)
>
> ----------------------------------------------------------------
>
> Platform data changes for omaps for the display subsystem and
> n900 secure mode changes. Note that the n900 secure mode changes
> will still be needed for device tree based booting also.
>
> ----------------------------------------------------------------

Thanks, pulled into next/boards.

Kevin

       reply	other threads:[~2013-10-14 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5258a9a9.0325310a.6fb0.ffffa1b2SMTPIN_ADDED_MISSING@mx.google.com>
2013-10-14 22:48 ` Kevin Hilman [this message]
2013-10-12  1:44 [GIT PULL 1/6] omap non-urgent fixes for v3.13 merge window Tony Lindgren
2013-10-12  1:44 ` [GIT PULL 5/6] omap display and board pdata 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=871u3n4gfd.fsf@linaro.org \
    --to=khilman@linaro.org \
    --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;
as well as URLs for NNTP newsgroup(s).