From: Wadim Egorov <w.egorov@phytec.de>
To: Mark Brown <broonie@kernel.org>
Cc: "Heiko Stübner" <heiko@sntech.de>,
linux-rockchip@lists.infradead.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, a.zummo@towertech.it,
pawel.moll@arm.com, rtc-linux@googlegroups.com,
ijc+devicetree@hellion.org.uk, mturquette@baylibre.com,
sboyd@codeaurora.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, lgirdwood@gmail.com,
alexandre.belloni@free-electrons.com, dianders@chromium.org,
galak@codeaurora.org, zyw@rock-chips.com, lee.jones@linaro.org,
linux-clk@vger.kernel.org
Subject: [rtc-linux] Re: Applied "regulator: rk808: remove linear range definitions with a single range" to the regulator tree
Date: Wed, 27 Apr 2016 16:06:08 +0200 [thread overview]
Message-ID: <5720C750.3050104@phytec.de> (raw)
In-Reply-To: <20160427135048.GQ3217@sirena.org.uk>
On 27.04.2016 15:50, Mark Brown wrote:
> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
>> On 26.04.2016 21:33, Heiko St=C3=BCbner wrote:
>>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on=20
>>> rk3288-veyron devices with the bug below. Reverting this one patch
>>> results in the system booting again:
>> This is because I missed to add the correct ops for LDO_REG3 in this pat=
ch.
> Any ETA on a fix or should I revert?
this patch
http://lists.infradead.org/pipermail/linux-rockchip/2016-April/008674.html
will fix the issue.
The regulator patches from v4 are based on top of
commit 4a5ed8c1adc3 ("regulator: rk808: remove unused rk808_reg_ops_ranges"=
)
--=20
--=20
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---=20
You received this message because you are subscribed to the Google Groups "=
rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-04-27 14:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 13:20 [rtc-linux] [PATCH v3 0/8] Add support for rk818 Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 1/8] drivers: mfd: rk808: rename rk808 struct to rk8xx Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 2/8] mfd: RK808: Add RK818 support Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 3/8] regulator: rk808: remove linear range definitions with a single range Wadim Egorov
2016-04-25 17:56 ` [rtc-linux] Applied "regulator: rk808: remove linear range definitions with a single range" to the regulator tree Mark Brown
2016-04-26 19:33 ` [rtc-linux] " Heiko Stübner
2016-04-27 6:35 ` Wadim Egorov
2016-04-27 13:50 ` Mark Brown
2016-04-27 13:56 ` Heiko Stübner
2016-04-27 16:41 ` Mark Brown
2016-04-27 14:06 ` Wadim Egorov [this message]
2016-04-26 10:46 ` [rtc-linux] Re: [PATCH v3 3/8] regulator: rk808: remove linear range definitions with a single range Mark Brown
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's simplified DT parsing code Wadim Egorov
2016-04-25 17:39 ` [rtc-linux] " Mark Brown
2016-04-26 7:45 ` Wadim Egorov
2016-04-26 8:17 ` Heiko Stübner
2016-04-26 8:46 ` Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 5/8] regulator: rk808: Add regulator driver for RK818 Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 6/8] mfd: dt-bindings: Add RK818 device tree bindings document Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 7/8] clk: Kconfig: Name RK818 in Kconfig for COMMON_CLK_RK808 Wadim Egorov
2016-04-25 13:20 ` [rtc-linux] [PATCH v3 8/8] rtc: Kconfig: Name RK818 in Kconfig for RTC_DRV_RK808 Wadim Egorov
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=5720C750.3050104@phytec.de \
--to=w.egorov@phytec.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sboyd@codeaurora.org \
--cc=zyw@rock-chips.com \
/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