From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] mfd: axp209x: Drop the parent supplies field
Date: Wed, 24 Sep 2014 08:32:08 +0200 [thread overview]
Message-ID: <20140924063207.GP15315@lukather> (raw)
In-Reply-To: <1411243596-15117-3-git-send-email-maxime.ripard@free-electrons.com>
Hi Lee,
On Sat, Sep 20, 2014 at 10:06:35PM +0200, Maxime Ripard wrote:
> Now that the regulator code get its parent supplies purely from the DT, we can
> drop the parent supplies resources in the MFD driver.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Acked-by: Lee Jones <lee.jones@linaro.org>
I know you have given your acked-by already, but could you merge this
patch through your tree?
It doesn't have any depedency, so it should be rather safe to do so.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140924/eb60c0e2/attachment.sig>
next prev parent reply other threads:[~2014-09-24 6:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 20:06 [PATCH 0/3] sunxi: Add AXP209 regulator support Maxime Ripard
2014-09-20 20:06 ` [PATCH 1/3] regulator: axp20x: Use parent device as regulator configuration device Maxime Ripard
2014-09-23 1:18 ` Mark Brown
2014-09-20 20:06 ` [PATCH 2/3] mfd: axp209x: Drop the parent supplies field Maxime Ripard
2014-09-24 6:32 ` Maxime Ripard [this message]
2014-09-24 7:03 ` Lee Jones
2014-09-20 20:06 ` [PATCH 3/3] ARM: sun7i: cubieboard2: Enable the AXP209 Maxime Ripard
2014-09-25 10:05 ` Maxime Ripard
2014-10-03 8:49 ` Chen-Yu Tsai
2014-10-06 12:07 ` Maxime Ripard
2014-10-06 12:16 ` Chen-Yu Tsai
2014-10-06 13:25 ` Maxime Ripard
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=20140924063207.GP15315@lukather \
--to=maxime.ripard@free-electrons.com \
--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