From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sharpsl_pm refactor
Date: Fri, 07 Jul 2006 16:24:10 +0100 [thread overview]
Message-ID: <1152285850.5548.102.camel@localhost.localdomain> (raw)
In-Reply-To: <20060707140148.GB4239@ucw.cz>
On Fri, 2006-07-07 at 14:01 +0000, Pavel Machek wrote:
> > I'm unconvinced as to why collie needs an ifdef in there and looking at
> > what I think you're leading to, its ugly. Perhaps you could change the 2
> > to a variable set by the machine instead or something, depending upon
> > your intention.
>
> Well, I hate the if/else maze -- IMO returns are more readable. Anyway
> collie needs both count and time checks disabled, AFAICT.
To me it looks much worse after you changed it as I can understand it at
the moment and afterwards with the ifdefs in, I can't.
Ignoring that issue, why does collie need them disabled? Do they break
collie somehow or is this just because the sharp driver didn't do it?
I'd prefer to keep the charging techniques the same across as many of
the devices as we can and I can't see how this technique causes a
problem. The charging hardware and the battery is very similar across
the models (although you wouldn't believe it looking at the charging
driver).
Richard
next prev parent reply other threads:[~2006-07-07 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 11:48 [patch] sharpsl_pm refactor Pavel Machek
2006-07-07 12:16 ` Richard Purdie
2006-07-07 14:01 ` Pavel Machek
2006-07-07 15:24 ` Richard Purdie [this message]
2006-07-08 13:00 ` 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=1152285850.5548.102.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.