All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sedat Dilek <sedat.dilek@gmail.com>, stable@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	"Bjørn Mork" <bjorn@mork.no>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-3.16.y: acpi-battery fixes
Date: Sat, 13 Sep 2014 08:24:38 -0700	[thread overview]
Message-ID: <20140913152438.GA3072@kroah.com> (raw)
In-Reply-To: <CA+icZUW8vHj9_L-4WD0FR6mUTWW621T5O-Cd=fSJ_UoPX0BQUg@mail.gmail.com>

On Sat, Sep 13, 2014 at 02:52:52PM +0200, Sedat Dilek wrote:
> Hi Greg,
> 
> I hoped the acpi-fixes from [1] (especially [2]) would fix my shown
> "85% battery available", but a Ubuntu/trusty kernel reports the same
> (battery defect?).
> The 2nd revert is applicable, the 1st not, both are labeled with 3.16+.
> 
> Wanna pick them or have it already on your to-do?
> 
> Thanks.
> 
> Regards,
> - Sedat -
> 
> [1] http://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/log/?h=acpi-battery
> [2] http://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit/?h=acpi-battery&id=508b3c677601797f2d51df3df5caa436dd235cb9

First off, stable kernel questions should go to stable@vger.kernel.org,
not just to me.

Secondly, I don't understand what you are asking here.  What exact fix
in Linus's tree do you want to see in a stable backport that I haven't
taken already?  I've queued up a number of ACPI fixes for 3.16.3, are
they not sufficient?

thanks,

greg k-h

  reply	other threads:[~2014-09-13 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 12:52 linux-3.16.y: acpi-battery fixes Sedat Dilek
2014-09-13 15:24 ` Greg Kroah-Hartman [this message]
2014-09-13 15:32   ` Sedat Dilek
2014-09-13 15:37     ` Greg Kroah-Hartman

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=20140913152438.GA3072@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bjorn@mork.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sedat.dilek@gmail.com \
    --cc=stable@vger.kernel.org \
    /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.