From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: dt changes for v3.13
Date: Wed, 09 Oct 2013 13:31:01 -0700 [thread overview]
Message-ID: <87mwmitce2.fsf@linaro.org> (raw)
In-Reply-To: <20130930162747.GH31178@titan.lakedaemon.net> (Jason Cooper's message of "Mon, 30 Sep 2013 12:27:47 -0400")
Jason Cooper <jason@lakedaemon.net> writes:
> Guys,
>
> Same as mvebu/drivers, these are the changes that missed the last
> window. All have been in -next since v3.12-rc1 without a problem.
>
Pulled into next/dt.
Thanks,
Kevin
prev parent reply other threads:[~2013-10-09 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 16:27 [GIT PULL] ARM: mvebu: dt changes for v3.13 Jason Cooper
2013-10-09 20:31 ` Kevin Hilman [this message]
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=87mwmitce2.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).