From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: hisi: soc changes for v4.11
Date: Wed, 25 Jan 2017 16:58:08 +0000 [thread overview]
Message-ID: <5888D920.2060900@hisilicon.com> (raw)
Hi Arnd, Hi Olof, Hi Kevin,
Please help to pull the following changes.
Thanks!
Best Regards,
Wei
---
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://github.com/hisilicon/linux-hisi.git tags/hisi-armv7-soc-for-4.11
for you to fetch changes up to 0ecac9f312f4e974614be5a9f56af2c8e892c897:
arm: hisi: drop extern hip01_cpu_die (2017-01-20 16:39:57 +0000)
----------------------------------------------------------------
ARM: mach-hisi: Hisilicon SoC updates for 4.11
- Drop the declaration of the unimplemented hip01_cpu_die
----------------------------------------------------------------
Kefeng Wang (1):
arm: hisi: drop extern hip01_cpu_die
arch/arm/mach-hisi/core.h | 1 -
1 file changed, 1 deletion(-)
next reply other threads:[~2017-01-25 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 16:58 Wei Xu [this message]
2017-01-30 1:31 ` [GIT PULL] ARM: hisi: soc changes for v4.11 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=5888D920.2060900@hisilicon.com \
--to=xuwei5@hisilicon.com \
--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).