From: Greg KH <greg@kroah.com>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: linux-acpi@vger.kernel.org, rui.zhang@intel.com,
stable@kernel.org, lenb@kernel.org
Subject: Re: [PATCH 2/6] ACPI / Battery: Change 16-bit signed negative battery current into correct value
Date: Wed, 29 Jun 2011 08:11:47 -0700 [thread overview]
Message-ID: <20110629151147.GC18023@kroah.com> (raw)
In-Reply-To: <1309335765-26475-1-git-send-email-tianyu.lan@intel.com>
On Wed, Jun 29, 2011 at 04:22:45PM +0800, Lan Tianyu wrote:
> This patch is for some machine which report the battery current
> as a 16-bit signed negative when it is charging. This is caused
> by DSDT bug. The commit bc76f90b8a5cf4aceedf210d08d5e8292f820cec
> has resolved the problem for Acer laptops. But some other machines
> also have such problem.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=33722
>
> Since it is improssible that the current is above 32A on laptops
> whether on AC or on battery, this patch is to check the current and
> take its absolute value as current and producing a message when it
> is negative in s16.
>
> Remove Acer quirk, as this workaround handles Acer too.
>
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
> ---
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
Same goes for the other patches in this series that you sent to
stable@kernel.org as well, please redo them.
_______________________________________________
stable mailing list
stable@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/stable
prev parent reply other threads:[~2011-06-29 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 8:22 [PATCH 2/6] ACPI / Battery: Change 16-bit signed negative battery current into correct value Lan Tianyu
2011-06-29 15:11 ` Greg KH [this message]
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=20110629151147.GC18023@kroah.com \
--to=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@kernel.org \
--cc=tianyu.lan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox