From: Anton Vorontsov <cbou@mail.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
vladimir.p.lebedev@intel.com,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] CodingStyle: Add information about trailing whitespace.
Date: Fri, 29 Jun 2007 23:31:18 +0400 [thread overview]
Message-ID: <20070629193118.GA2108@zarina> (raw)
In-Reply-To: <1183142639.1170.371.camel@pmac.infradead.org>
On Fri, Jun 29, 2007 at 07:43:59PM +0100, David Woodhouse wrote:
> On Fri, 2007-06-29 at 21:52 +0400, Anton Vorontsov wrote:
> > Andrew, regarding git-battery-vs-git-acpi.patch.. I'll merge it as
> > soon as acpi related changes will hit Linus tree, would that be okay
> > for you? Not that I don't like these changes, I do like them. But
> > they'll break bare battery2-2.6 (based on Linus tree). Though, I can
> > merge it now if that will make your living easier.
>
> Was anyone working on hooking up APM and ACPI to the new battery class,
> btw?
Don't know of anyone yet. But lets inquire appropriate people, I don't have
x86 hardware with batteries, thus I hardly can help on that matter, nor
following any x86 development.
Henrique de Moraes Holschuh (IBM ACPI EXTRAS maintainer) was involved in
battery class review, Cc'ed. Also Cc'ing ACPI BATTERY maintainer, and
linux-acpi list.
Just reminder: we're talking about power supply class, its git tree
is at git://git.infradead.org/users/cbou/battery2-2.6.git, you may also
find it in recent -mm patchsets. Most interesting directory is
drivers/power/, contains power supply class and drivers, plus header
file at include/linux/power_supply.h. Also,
Documentation/power_supply_class.txt exits.
Thanks,
--
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.org/bd2
next prev parent reply other threads:[~2007-06-29 19:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 17:59 [PATCH] CodingStyle: Add information about trailing whitespace Josh Triplett
2007-06-27 18:05 ` Chris Shoemaker
2007-06-27 18:17 ` Josh Triplett
2007-06-27 19:32 ` Chris Shoemaker
2007-06-27 22:18 ` Jan Engelhardt
2007-06-28 6:00 ` dave young
2007-06-28 6:08 ` Josh Triplett
2007-06-28 6:29 ` dave young
2007-06-28 6:52 ` Jan Engelhardt
2007-06-28 6:58 ` Josh Triplett
2007-06-28 7:08 ` Li Yang-r58472
2007-06-28 7:10 ` Dave Young
2007-06-28 7:20 ` Dave Young
2007-06-29 3:11 ` [OT] Vim highlighting for trailing spaces Kyle Moffett
2007-06-29 7:39 ` Jan Engelhardt
2007-06-29 7:53 ` Josh Triplett
2007-06-29 8:01 ` Jan Engelhardt
2007-06-29 8:42 ` Josh Triplett
2007-06-29 9:21 ` Björn Steinbrink
2007-06-29 9:26 ` Dave Young
2007-06-29 12:40 ` Michael Tokarev
2007-06-29 12:49 ` Dmitry Torokhov
2007-06-30 0:00 ` Kyle Moffett
2007-06-29 2:03 ` [PATCH] CodingStyle: Add information about trailing whitespace Andy Isaacson
2007-06-27 19:31 ` Andrew Morton
2007-06-27 22:14 ` Jan Engelhardt
2007-06-27 22:14 ` Oleg Verych
[not found] ` <1183138323.17622.9.camel@shinybook.infradead.org>
[not found] ` <20070629175204.GA1341@zarina>
[not found] ` <1183142639.1170.371.camel@pmac.infradead.org>
2007-06-29 19:31 ` Anton Vorontsov [this message]
2007-06-29 22:52 ` Henrique de Moraes Holschuh
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=20070629193118.GA2108@zarina \
--to=cbou@mail.ru \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=vladimir.p.lebedev@intel.com \
/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.