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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
