Linux RTC
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Wadim Egorov <w.egorov@phytec.de>
Cc: 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 3/8] regulator: rk808: remove linear range definitions with a single range
Date: Tue, 26 Apr 2016 11:46:45 +0100	[thread overview]
Message-ID: <20160426104645.GU3217@sirena.org.uk> (raw)
In-Reply-To: <1461590448-47685-4-git-send-email-w.egorov@phytec.de>

[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]

On Mon, Apr 25, 2016 at 03:20:43PM +0200, Wadim Egorov wrote:
> The driver was using only linear ranges. Now we remove linear range
> definitions with a single range. So we have to add an ops struct for
> ranges and adjust all other ops functions accordingly.

This and some other cleanups are now available as a signed tag from my
repository:

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

  Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-rk808-cleanups

for you to fetch changes up to 4a5ed8c1adc39f86a2887183c71b007bc962fdce:

  regulator: rk808: remove unused rk808_reg_ops_ranges (2016-04-26 11:11:29 +0100)

----------------------------------------------------------------
regulator: rk808: Some cleanups for the rk808 driver

These are tagged to facilitate the addition of support for the rk818
which may end up overlapping with some of these cleanups.

----------------------------------------------------------------
Arnd Bergmann (1):
      regulator: rk808: remove unused rk808_reg_ops_ranges

Wadim Egorov (1):
      regulator: rk808: remove linear range definitions with a single range

 drivers/regulator/rk808-regulator.c | 66 ++++++++++++++-----------------------
 1 file changed, 25 insertions(+), 41 deletions(-)

-- 
-- 
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.
--- 
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 email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-04-26 10:46 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   ` Mark Brown [this message]
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=20160426104645.GU3217@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=galak@codeaurora.org \
    --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=w.egorov@phytec.de \
    --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