All of lore.kernel.org
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch] zaurus family: battery cleanups
Date: Fri, 11 Sep 2009 21:56:35 +0200	[thread overview]
Message-ID: <20090911195635.GD8137@elf.ucw.cz> (raw)
In-Reply-To: <1252507631.14793.113.camel@desktop>

On Wed 2009-09-09 07:47:11, Daniel Walker wrote:
> On Wed, 2009-09-09 at 09:39 +0200, Pavel Machek wrote:
> > This cleans up battery code to conform to codingstyle. The only real
> > change is that we should now refuse to charge if we can't read battery
> > temperature.
> 
> This patch has a number of checkpatch errors. Mostly trailing
> whitespace, or just spacing issues..

Well, original code has problems, too, and I'm trying to slowly clean
that up.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Walker <dwalker@fifo99.com>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>,
	Dirk@Opfer-Online.de, arminlitzel@web.de,
	Cyril Hrubis <metan@ucw.cz>,
	thommycheck@gmail.com,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	dbaryshkov@gmail.com, omegamoon@gmail.com, eric.y.miao@gmail.com,
	utx@penguin.cz, Russell King <rmk@arm.linux.org.uk>
Subject: Re: [patch] zaurus family: battery cleanups
Date: Fri, 11 Sep 2009 21:56:35 +0200	[thread overview]
Message-ID: <20090911195635.GD8137@elf.ucw.cz> (raw)
In-Reply-To: <1252507631.14793.113.camel@desktop>

On Wed 2009-09-09 07:47:11, Daniel Walker wrote:
> On Wed, 2009-09-09 at 09:39 +0200, Pavel Machek wrote:
> > This cleans up battery code to conform to codingstyle. The only real
> > change is that we should now refuse to charge if we can't read battery
> > temperature.
> 
> This patch has a number of checkpatch errors. Mostly trailing
> whitespace, or just spacing issues..

Well, original code has problems, too, and I'm trying to slowly clean
that up.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-09-11 19:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  7:39 [patch] zaurus family: battery cleanups Pavel Machek
2009-09-09  7:39 ` Pavel Machek
2009-09-09 14:47 ` Daniel Walker
2009-09-09 14:47   ` Daniel Walker
2009-09-11 19:56   ` Pavel Machek [this message]
2009-09-11 19:56     ` Pavel Machek
2009-09-11 21:04     ` Daniel Walker
2009-09-11 21:04       ` Daniel Walker
2009-09-15 12:45 ` [patch v2] " Pavel Machek
2009-09-15 12:45   ` Pavel Machek

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=20090911195635.GD8137@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.