mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Kevin Liu <keyuan.liu@gmail.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	kyungmin.park@samsung.com,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	lrg@ti.com, Philip Rakity <prakity@nvidia.com>
Subject: Re: FW: [PATCH v2] mmc: sdhci: apply voltage range check only for non-fixed regulators
Date: Fri, 30 Nov 2012 11:48:59 -0500	[thread overview]
Message-ID: <87hao7f344.fsf@octavius.laptop.org> (raw)
In-Reply-To: <50AB9B90.1030404@samsung.com> (Marek Szyprowski's message of "Tue, 20 Nov 2012 16:02:40 +0100")

Hi Marek,

On Tue, Nov 20 2012, Marek Szyprowski wrote:
> The problem with dummy regulator is the fact that it can be enabled only
> globally for all devices in the system. I think that the best solution
> would be to introduce regulator_can_change_voltage() as Mark suggested.
> I will post patches soon.

Does this mean that I shouldn't merge either yours or Kevin's patch for
3.8, while we wait for this?  Any ETA on it?

Thanks very much,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  parent reply	other threads:[~2012-11-30 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <25B60CDC2F704E4E9D88FFD52780CB4C060FBEA29A@SC-VEXCH1.marvell.com>
2012-11-14  7:11 ` Kevin Liu
2012-11-14  7:28   ` Mark Brown
2012-11-14  8:36     ` Kevin Liu
2012-11-14  8:41       ` Mark Brown
2012-11-14  8:57         ` Kevin Liu
2012-11-14  9:08           ` Philip Rakity
2012-11-14 12:05             ` Kevin Liu
2012-11-20  7:44   ` FW: " Marek Szyprowski
2012-11-20  8:59     ` Kevin Liu
2012-11-20 10:16       ` Marek Szyprowski
2012-11-20 11:36         ` Kevin Liu
2012-11-20 13:12           ` Marek Szyprowski
2012-11-20 13:27             ` Chris Ball
2012-11-20 14:14             ` Kevin Liu
2012-11-20 15:02               ` Marek Szyprowski
2012-11-20 15:24                 ` Kevin Liu
2012-11-30 16:48                 ` Chris Ball [this message]
2012-12-04 14:07                   ` Marek Szyprowski

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=87hao7f344.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=keyuan.liu@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=m.szyprowski@samsung.com \
    --cc=prakity@nvidia.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
Powered by JetHome