From: Len Brown <lenb@kernel.org>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Linux-acpi@vger.kernel.org
Subject: Re: [RFC][PATCH] ACPI: battery: add power_{now, avg} properties to power_class
Date: Tue, 16 Dec 2008 12:41:41 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812161237220.4414@localhost.localdomain> (raw)
In-Reply-To: <20081216162756.12100.49260.stgit@thinkpad>
On Tue, 16 Dec 2008, Alexey Starikovskiy wrote:
> +What: current_{now,avg} attributes for batteries, reporting in energy units
> +When: 2.6.29
> +Why: Batteries, reporting in energy units, will report (dis)charge rate as
> + power (Watts), and not as current (Amperes), thus new power_{now,avg}
> + attributes should be used for such batteries to avoid the confusion.
> +Who: Alexey Starikovskiy <astarikovskiy@suse.de>
I think that a single kernel release cycle is too quick
for a user/kernel API change unless you're trying to fix
something that is new and you have a pretty good idea
that nobody is using it yet. Kernel programmers typically
want to talk about O(6 months) and Linus comes back and
talks aboutg O(10 years)...
-- Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2008-12-16 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 16:27 [RFC][PATCH] ACPI: battery: add power_{now, avg} properties to power_class Alexey Starikovskiy
2008-12-16 17:41 ` Len Brown [this message]
2008-12-16 20:49 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2008-12-15 21:38 Alexey Starikovskiy
2008-12-16 1:22 ` Henrique de Moraes Holschuh
2008-12-16 8:53 ` Alexey Starikovskiy
2008-12-16 14:18 ` Henrique de Moraes Holschuh
2008-12-16 15:19 ` Rafael J. Wysocki
2008-12-16 15:17 ` Rafael J. Wysocki
2008-12-16 15:28 ` Alexey Starikovskiy
2008-12-16 15:51 ` Rafael J. Wysocki
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=alpine.LFD.2.00.0812161237220.4414@localhost.localdomain \
--to=lenb@kernel.org \
--cc=Linux-acpi@vger.kernel.org \
--cc=astarikovskiy@suse.de \
/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