From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [GIT PULL 1/3] 2nd part of rockchip soc-driver changes for 4.6
Date: Fri, 04 Mar 2016 02:39:50 +0100 [thread overview]
Message-ID: <2165258.7vUftGQ1I7@diego> (raw)
Hi Arnd, Olof, Kevin,
this contains a fix for the error handling of the power-domain driver.
Thanks
Heiko
The following changes since commit 1d961f11a108af9f7fbe89cc950a8d16ddbdbb28:
soc: rockchip: power-domain: fix err handle while probing (2016-02-02 22:18:31 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.6-rockchip-drivers2
for you to fetch changes up to 1503cfbbc7c62509c9b1188508d312ab9c90cb24:
soc: rockchip: power-domain: check the existing of regmap (2016-02-15 22:24:14 +0100)
----------------------------------------------------------------
Fix handling the case when syscon_node_to_regmap returns an error
in the power-domain driver.
----------------------------------------------------------------
Shawn Lin (1):
soc: rockchip: power-domain: check the existing of regmap
drivers/soc/rockchip/pm_domains.c | 4 ++++
1 file changed, 4 insertions(+)
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] 2nd part of rockchip soc-driver changes for 4.6
Date: Fri, 04 Mar 2016 02:39:50 +0100 [thread overview]
Message-ID: <2165258.7vUftGQ1I7@diego> (raw)
Hi Arnd, Olof, Kevin,
this contains a fix for the error handling of the power-domain driver.
Thanks
Heiko
The following changes since commit 1d961f11a108af9f7fbe89cc950a8d16ddbdbb28:
soc: rockchip: power-domain: fix err handle while probing (2016-02-02 22:18:31 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.6-rockchip-drivers2
for you to fetch changes up to 1503cfbbc7c62509c9b1188508d312ab9c90cb24:
soc: rockchip: power-domain: check the existing of regmap (2016-02-15 22:24:14 +0100)
----------------------------------------------------------------
Fix handling the case when syscon_node_to_regmap returns an error
in the power-domain driver.
----------------------------------------------------------------
Shawn Lin (1):
soc: rockchip: power-domain: check the existing of regmap
drivers/soc/rockchip/pm_domains.c | 4 ++++
1 file changed, 4 insertions(+)
next reply other threads:[~2016-03-04 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 1:39 Heiko Stuebner [this message]
2016-03-04 1:39 ` [GIT PULL 1/3] 2nd part of rockchip soc-driver changes for 4.6 Heiko Stuebner
2016-03-04 1:42 ` [GIT PULL 2/3] 2nd part of rockchip dts32 " Heiko Stübner
2016-03-04 1:42 ` Heiko Stübner
2016-03-04 1:43 ` [GIT PULL 3/3] 2nd part of rockchip dts64 " Heiko Stübner
2016-03-04 1:43 ` Heiko Stübner
2016-03-15 15:30 ` [GIT PULL 1/3] 2nd part of rockchip soc-driver " Heiko Stübner
2016-03-15 15:30 ` Heiko Stübner
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=2165258.7vUftGQ1I7@diego \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.