public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] 2nd part of rockchip soc-driver changes for 4.6
Date: Tue, 15 Mar 2016 16:30:45 +0100	[thread overview]
Message-ID: <4293420.gm3Wdi1Lsl@diego> (raw)
In-Reply-To: <2165258.7vUftGQ1I7@diego>

Hi,

please scrap these 3 pull requests. I'm migrating the commits to v4.7 in my 
tree.


Thanks
Heiko

Am Freitag, 4. M?rz 2016, 02:39:50 schrieb Heiko Stuebner:
> 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(+)

      parent reply	other threads:[~2016-03-15 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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:43 ` [GIT PULL 3/3] 2nd part of rockchip dts64 " Heiko Stübner
2016-03-15 15:30 ` Heiko Stübner [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=4293420.gm3Wdi1Lsl@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