From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL RESEND 2/4] Rockchip soc32 changes for 4.17
Date: Wed, 28 Mar 2018 17:08:45 +0200 [thread overview]
Message-ID: <4643567.9MCT7BxVJK@diego> (raw)
In-Reply-To: <12470502.BUvxkRrZk8@phil>
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/
v4.17-rockchip-soc32-1
for you to fetch changes up to 03151b8989257bfcee6cfd5f06d9a4a06b781cf3:
ARM: rockchip: Set name of pmu regmap_config in smp code (2018-03-12
11:09:36 +0100)
----------------------------------------------------------------
Fix for the legacy pmu-regmap in the smp-code to have a real name
and therefore not create a dummy* entry in debugfs.
----------------------------------------------------------------
Jeffy Chen (1):
ARM: rockchip: Set name of pmu regmap_config in smp code
arch/arm/mach-rockchip/platsmp.c | 1 +
1 file changed, 1 insertion(+)
next prev parent reply other threads:[~2018-03-28 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 22:20 [GIT PULL 1/4] Rockchip driver changes for 4.17 Heiko Stuebner
2018-03-15 22:21 ` [GIT PULL 2/4] Rockchip soc32 " Heiko Stuebner
2018-03-15 22:22 ` [GIT PULL 3/4] Rockchip dts32 " Heiko Stuebner
2018-03-15 22:22 ` [GIT PULL 4/4] Rockchip dts64 " Heiko Stuebner
2018-03-27 17:50 ` [GIT PULL 1/4] Rockchip driver " Heiko Stübner
2018-03-28 15:10 ` Arnd Bergmann
2018-03-28 15:08 ` Heiko Stuebner [this message]
2018-03-28 15:15 ` [GIT PULL RESEND 2/4] Rockchip soc32 " Arnd Bergmann
2018-03-28 15:09 ` [GIT PULL RESEND 3/4] Rockchip dts32 " Heiko Stuebner
2018-03-28 15:16 ` Arnd Bergmann
2018-03-28 15:09 ` [GIT PULL RESEND 4/4] Rockchip dts64 " Heiko Stuebner
2018-03-28 15:17 ` Arnd Bergmann
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=4643567.9MCT7BxVJK@diego \
--to=heiko@sntech.de \
--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).