From: James Kosin <jkosin@beta.intcomgrp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Brown <broonie@sirena.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [RFD] voltage/current regulator consumer interface
Date: Wed, 22 Apr 2009 11:00:05 -0400 [thread overview]
Message-ID: <49EF30F5.7030108@beta.intcomgrp.com> (raw)
In-Reply-To: <20090422154920.0dda2380@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
Alan Cox wrote:
>>> In power management line normally refers to the core, unregulated power
>>> bus for the system and a line supply would normally be something like a
>>> wall wart that supplies this directly when it's connected.
>> Can I suggest:
>> "supply-switch" or "regulator-switch" may make more sense for the moment.
>
> Can I suggest they don't. The naming should reflect the naming actually
> used in the field by people working on the technology otherwise arbitary
> renaming just creates confusion
>
> The supply switch is the big switch on the back
>
> Alan
>
Ok, "supply-switch" may have been a bad idea, I wasn't thinking yet.
The coffee hasn't kicked in yet and I'm feeling a bit down.
James
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
next prev parent reply other threads:[~2009-04-22 15:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ct38K-3Fq-11@gated-at.bofh.it>
2009-04-20 15:38 ` [RFD] voltage/current regulator consumer interface James Kosin
2009-04-21 6:07 ` Mike Rapoport
2009-04-21 13:25 ` James Kosin
2009-04-21 14:05 ` Mike Rapoport
2009-04-21 14:31 ` James Kosin
2009-04-25 8:19 ` Pavel Machek
2009-04-25 9:04 ` Mark Brown
2009-04-27 13:47 ` James Kosin
2009-04-27 14:21 ` Mark Brown
2009-04-21 14:30 ` Mark Brown
2009-04-21 10:05 ` Mark Brown
[not found] ` <ct38K-3Fq-9@gated-at.bofh.it>
[not found] ` <ctmXD-1yA-3@gated-at.bofh.it>
[not found] ` <ctnK4-2zP-11@gated-at.bofh.it>
[not found] ` <ctoG9-458-7@gated-at.bofh.it>
[not found] ` <ctoG9-458-5@gated-at.bofh.it>
[not found] ` <ctoPK-4y5-5@gated-at.bofh.it>
[not found] ` <ctoZv-4KN-23@gated-at.bofh.it>
[not found] ` <ctFxn-5OC-11@gated-at.bofh.it>
[not found] ` <ctG0r-6HL-31@gated-at.bofh.it>
2009-04-22 14:31 ` James Kosin
2009-04-22 14:49 ` Alan Cox
2009-04-22 15:00 ` James Kosin [this message]
2009-04-20 14:32 Mike Rapoport
2009-04-20 14:56 ` Mark Brown
2009-04-21 12:00 ` Mike Rapoport
2009-04-21 12:55 ` Mark Brown
2009-04-21 13:54 ` Mike Rapoport
2009-04-21 13:56 ` Mark Brown
2009-04-21 14:01 ` Mike Rapoport
2009-04-21 14:14 ` Mark Brown
2009-04-22 7:57 ` Mike Rapoport
2009-04-22 8:26 ` 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=49EF30F5.7030108@beta.intcomgrp.com \
--to=jkosin@beta.intcomgrp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@sirena.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).