mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Donggeun Kim <dg77.kim@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-pm@vger.kernel.org, len.brown@intel.com, pavel@ucw.cz,
	rjw@sisk.pl, rdunlap@xenotime.net, cbouatmailru@gmail.com,
	pali.rohar@gmail.com, prakity@mavell.com, lars@metafoo.de,
	kyungmin.park@samsung.com, myungjoo.ham@samsung.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] power: introduce Charger-Manager
Date: Wed, 28 Dec 2011 13:48:16 +0900	[thread overview]
Message-ID: <4EFA9F90.8090204@samsung.com> (raw)
In-Reply-To: <20111227105555.GG2870@opensource.wolfsonmicro.com>

On 2011년 12월 27일 19:55, Mark Brown wrote:
> On Tue, Dec 27, 2011 at 06:47:47PM +0900, Donggeun Kim wrote:
> 
>> Changes for v3:
>>     - rename variables and functions
>>     - clean up code
>>     - add build dependency of RTC_CLASS and REGULATOR
> 
> Does it actually depend on REGULATOR?  It looks like it just uses get
> and enable which are stubbed out automatically by the API.
> 
If CONFIG_REGULATOR is not defined,
compile error occurs because charger-manager calls
'regulator_force_disable' function.

Thanks.
-Donggeun

  reply	other threads:[~2011-12-28  4:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27  9:47 Donggeun Kim
2011-12-27  9:47 ` [PATCH v3 1/2] power: Charger-Manager: add initial Charger-Manager driver Donggeun Kim
2011-12-27 11:36   ` Mark Brown
2011-12-28  5:00     ` Donggeun Kim
2011-12-27  9:47 ` [PATCH v3 2/2] power: Charger-Manager: add properties for power-supply-class Donggeun Kim
2011-12-27 10:55 ` [PATCH v3 0/2] power: introduce Charger-Manager Mark Brown
2011-12-28  4:48   ` Donggeun Kim [this message]
2011-12-28 11:05     ` Mark Brown
2012-01-02  9:49       ` [PATCH] regulator: add regulator_force_disable() definition for !CONFIG_REGULATOR MyungJoo Ham
2012-01-02 11:40         ` Mark Brown
2012-01-04  4:11 ` [PATCH v3 0/2] power: introduce Charger-Manager Anton Vorontsov

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=4EFA9F90.8090204@samsung.com \
    --to=dg77.kim@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cbouatmailru@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lars@metafoo.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=prakity@mavell.com \
    --cc=rdunlap@xenotime.net \
    --cc=rjw@sisk.pl \
    /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