Linux RTC
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	rtc-linux@googlegroups.com, devicetree@vger.kernel.org,
	linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	mturquette@baylibre.com, sboyd@codeaurora.org,
	lee.jones@linaro.org, lgirdwood@gmail.com, a.zummo@towertech.it,
	alexandre.belloni@free-electrons.com, dianders@chromium.org,
	zyw@rock-chips.com
Subject: [rtc-linux] Re: [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's simplified DT parsing code
Date: Tue, 26 Apr 2016 10:46:54 +0200	[thread overview]
Message-ID: <571F2AFE.2020006@phytec.de> (raw)
In-Reply-To: <2669414.IKg01zC8vG@diego>



On 26.04.2016 10:17, Heiko St=C3=BCbner wrote:
> Am Dienstag, 26. April 2016, 09:45:56 schrieb Wadim Egorov:
>> On 25.04.2016 19:39, Mark Brown wrote:
>>> On Mon, Apr 25, 2016 at 03:20:44PM +0200, Wadim Egorov wrote:
>>>> A common simplified DT parsing code for regulators was introduced in
>>>> commit a0c7b164ad11 ("regulator: of: Provide simplified DT parsing
>>>> method")
>>> This doesn't apply against current code, please check and resend.
>> Hm, for me all patches apply to the current code.
>> This patch depends on the first rename patch. Maybe this is the problem?
> which is the reason why renaming stuff makes everything just more complic=
ated=20
> without providing additional value ;-)=20
>
> The first patch would go through the mfd-tree (if accepted by Lee and Ack=
ed by=20
> the other involved subsystem maintainers) which would then need a stable=
=20
> branch merged into the regulator tree - or after the first patch goes in =
you=20
> simply wait for a kernel release.
>
> Normally I would expect the reasonable kernel developer to be able to sim=
ply=20
> read code, kconfig, docs stating the drivers being for rk808 and rk818 wi=
thout=20
> getting "confused" by some structs mentioning the rk808.
>
>
> Heiko
I will drop the first patch and send a v4 later

--=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.

  reply	other threads:[~2016-04-26  8:47 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
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 [this message]
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=571F2AFE.2020006@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