All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Adrian von Bidder <avbidder@fortytwo.ch>
Cc: Peter Feuerer <peter@piie.net>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: acerhdf: stilll fighting between kernel and BIOS?
Date: Tue, 01 Dec 2009 08:43:35 +0200	[thread overview]
Message-ID: <4B14BB17.9010600@cs.helsinki.fi> (raw)
In-Reply-To: <200911301902.42262@fortytwo.ch>

Adrian von Bidder kirjoitti:
> On Monday 23 November 2009 10.58:54 Pekka Enberg wrote:
>> On Mon, Nov 23, 2009 at 11:17 AM, Adrian von Bidder
>>
>> <avbidder@fortytwo.ch> wrote:
>>> Heyho!
>>>
>>> On Sunday 22 November 2009 22.27:50 Peter Feuerer wrote:
>>>> issues with AOA 150 netbooks should be solved with current 2.6.32-git
>>>>  tree. You can also try to use latest acerhdf of http://piie.net
>>> Seems to work fine.  That was the fix I thought was already included in
>>> 2.6.31.
>> Is that commit ded0cdfc6a7673916b0878c32fa8ba566b4f8cdb ("acerhdf: fix
>> fan control for AOA150 model")? Should it go to -stable?
> 
> Sorry for not answering sooner.
> 
> I don't really have time to recompile / test more at this time; in any case, 
> I think it's just a minor annoyance and not what I'd feed into a "fixes 
> only" tree.  (I'm not involved in kernel development in any way, but I 
> thought that the stable tree should be quite limited in what goes in?)

Your call. The rules of stable are pretty simple: (1) the patch needs to 
fix a _real_ problem and (2) it needs to be rather small. AFAICT, both 
apply here.

			Pekka

      reply	other threads:[~2009-12-01  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20  7:23 acerhdf: stilll fighting between kernel and BIOS? Adrian von Bidder
2009-11-22 21:27 ` Peter Feuerer
2009-11-23  9:17   ` Adrian von Bidder
2009-11-23  9:58     ` Pekka Enberg
2009-11-30 18:02       ` Adrian von Bidder
2009-12-01  6:43         ` Pekka Enberg [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=4B14BB17.9010600@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=avbidder@fortytwo.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@piie.net \
    --cc=stable@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.