public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [RESEND PATCH v2 0/2] power_supply: update Charger-Manager
Date: Mon, 07 May 2012 10:11:49 +0900	[thread overview]
Message-ID: <4FA72155.8020301@samsung.com> (raw)
In-Reply-To: <20120506025623.GA8437@lizard>

Hi Anton,

Firstly, thank for your reply and applied.

On 05/06/2012 11:56 AM, Anton Vorontsov wrote:
> On Tue, Apr 24, 2012 at 07:47:24PM +0900, Chanwoo Choi wrote:
> [...]
>>  Documentation/power/charger-manager.txt |   41 +++-
>>  drivers/power/charger-manager.c         |  391
>> +++++++++++++++++++++++++++++++
>>  include/linux/power/charger-manager.h   |   49 ++++-
>>  3 files changed, 471 insertions(+), 10 deletions(-)
> 
> Applied, thanks!
> 
> Note that the patches were word-wrap damaged, I had to fix them by
> hand. The file 'linux/Documentation/email-clients.txt' contains some
> useful tips for setting up commonly used mail clients. You might
> also try using 'git send-email'.

I'm so sorry. I will not do a same mistake.

> 
> While looking through the CM code, I noticed that cm uevents
> are not friendly wrt several chargers (the code has static variables
> in the uevent_notify() func).
> 
I will modify obscure code about your comment in the next patch.

> Also, what's the rationale behind implementing own uevent handling,
> and not using power_supply uevents (see power_supply_sysfs.c
> and power_supply_changed() thing)? Also, you don't seem to
> report variables in the uevent, but just messages. That's unusual.
> 
OK, I will implement uevent feature in charger-manager by using
power_supply uevents
instead of own uevent handling and post new patchset.

Best Regards,
Chanwoo Choi


      reply	other threads:[~2012-05-07  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 12:07 [PATCH v2 0/2] power_supply: update Charger-Manager Chanwoo Choi
2012-04-06  0:31 ` [RESEND PATCH " Chanwoo Choi
2012-04-24 10:47   ` Chanwoo Choi
2012-05-06  2:56     ` Anton Vorontsov
2012-05-07  1:11       ` Chanwoo Choi [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=4FA72155.8020301@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=cbouatmailru@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --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