From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] CSR SiRFSoC DT for 4.3
Date: Tue, 11 Aug 2015 15:10:15 +0200 [thread overview]
Message-ID: <20150811131015.GE30181@localhost> (raw)
In-Reply-To: <CAGsJ_4yxiytb3bUVsG5jTWKQdY7xE8HKBz7Og_Se=mB_cr3ZEQ@mail.gmail.com>
On Wed, Aug 05, 2015 at 03:15:08PM +0800, Barry Song wrote:
> Hi Arnd, Kevin, Olof,
>
> The following changes since commit bc0195aad0daa2ad5b0d76cce22b167bc3435590:
>
> Linux 4.2-rc2 (2015-07-12 15:10:30 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/baohua/linux.git
> tags/sirf-dts-for-4.3
>
> for you to fetch changes up to 2cd212427fa9cbf19c1f353d6e14b959e8f112f7:
>
> ARM: dts: atlas7: add a GPIO key for rearview button (2015-08-05
> 22:44:21 +0800)
Thanks, merged.
-Olof
prev parent reply other threads:[~2015-08-11 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 7:15 [GIT PULL] CSR SiRFSoC DT for 4.3 Barry Song
2015-08-11 13:10 ` Olof Johansson [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=20150811131015.GE30181@localhost \
--to=olof@lixom.net \
--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).