From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] regulator: rename function regulator_register_fixed
Date: Sat, 31 Mar 2012 14:45:16 +0100 [thread overview]
Message-ID: <20120331134515.GB5012@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120331125440.GA2395@S2101-09.ap.freescale.net>
On Sat, Mar 31, 2012 at 08:54:43PM +0800, Shawn Guo wrote:
> On Sat, Mar 31, 2012 at 11:25:08AM +0100, Mark Brown wrote:
> > There's no harm in using it for regulators that physically exist if
> > nothing cares about any of the information it can't provide
> I do not think it's practical for physical regulator to use the
> function, since the function forces microvolts to be 0.
Yeah, but it depends if anyone actually cares what the voltage is - most
consumers never look to see what the voltage is because they have no
reason to care. The lack of naming is more of an issue really.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120331/fd870d51/attachment.sig>
next prev parent reply other threads:[~2012-03-31 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 8:33 [PATCH 1/2] regulator: fix sysfs name collision between dummy and fixed dummy regulator Shawn Guo
2012-03-31 8:33 ` [PATCH 2/2] regulator: rename function regulator_register_fixed Shawn Guo
2012-03-31 10:25 ` Mark Brown
2012-03-31 12:54 ` Shawn Guo
2012-03-31 13:45 ` Mark Brown [this message]
2012-03-31 10:25 ` [PATCH 1/2] regulator: fix sysfs name collision between dummy and fixed dummy regulator Mark Brown
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=20120331134515.GB5012@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).