From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: dts: hisilicon: hi6220 hikey board updates for 4.8
Date: Tue, 5 Jul 2016 21:49:19 -0700 [thread overview]
Message-ID: <20160706044919.GI23212@localhost> (raw)
In-Reply-To: <5772B8AF.4040608@hisilicon.com>
On Tue, Jun 28, 2016 at 06:49:35PM +0100, Wei Xu wrote:
> Hi Arnd, Hi Olof, Hi Kevin,
>
> Please help to pull the following changes.
> Thanks!
>
> Best Regards,
> Wei
>
> ---
>
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
>
> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>
> are available in the git repository at:
>
> git://github.com/hisilicon/linux-hisi.git tags/hi6220-dt-for-4.8
>
> for you to fetch changes up to bbaf867e2d3796bca465d07ffcd800a3bd570861:
>
> arm64: dts: hikey: name the GPIO lines (2016-06-28 17:36:04 +0100)
>
> ----------------------------------------------------------------
> ARM64: DT: Hisilicon Hi6220 hikey board updates for 4.8
>
> - name the GPIO lines
>
> ----------------------------------------------------------------
> Linus Walleij (1):
> arm64: dts: hikey: name the GPIO lines
>
> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 143 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 143 insertions(+)
Merged into next/dt64. Thanks.
Also, as I've told others: If you redirect your git request-pull to a file, or
pipe it through cat, it'll produce a diffstat that is more reasonable for email
(80 columns).
-Olof
next prev parent reply other threads:[~2016-07-06 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 17:49 [GIT PULL] arm64: dts: hisilicon: hi6220 hikey board updates for 4.8 Wei Xu
2016-07-06 4:49 ` Olof Johansson [this message]
2016-07-06 8:33 ` Wei Xu
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=20160706044919.GI23212@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).