From: "Heiko Stübner" <heiko@sntech.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regulator: add a summary tree in debugfs
Date: Thu, 09 Apr 2015 01:33:59 +0200 [thread overview]
Message-ID: <2605479.kHV4CVBNQA@diego> (raw)
In-Reply-To: <20150408173825.GF6023@sirena.org.uk>
Am Mittwoch, 8. April 2015, 18:38:25 schrieb Mark Brown:
> On Tue, Apr 07, 2015 at 04:16:39PM +0200, Heiko Stübner wrote:
> > - output current-limit for current regulators
>
> What I meant here was that we should try to output the current limit for
> all regulators, not just for current regulators. I've applied this as
> is though since it's basically OK, can you send a followup please?
ah I didn't know regulator_get_current_limit() was valid for non
REGULATOR_CURRENT devices too.
Followup follows tomorrow - or today as I've just looked at the clock :-)
Heiko
prev parent reply other threads:[~2015-04-08 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 0:04 [PATCH] regulator: add a data summary tree in debugfs Heiko Stübner
2015-04-06 15:24 ` Mark Brown
2015-04-07 14:16 ` [PATCH v2] regulator: add a " Heiko Stübner
2015-04-08 17:38 ` Mark Brown
2015-04-08 23:33 ` 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=2605479.kHV4CVBNQA@diego \
--to=heiko@sntech.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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