public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Thomas Renninger <trenn@suse.de>
Cc: Stable <Stable@kernel.org>, Dmitry Torokhov <dtor@insightbb.com>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH - 2.6.19 -0/2] Backport of psmouse suspend/shutdown cleanups
Date: Wed, 21 Feb 2007 20:52:03 +0100	[thread overview]
Message-ID: <20070221195203.GF3732@elf.ucw.cz> (raw)
In-Reply-To: <1172077685.10619.101.camel@d36.suse.de>

Hi!

I'm not input or stable maintainer, but...

> I like to ask for inclusion into stable series for these.
> 
> The original patch from Dmitry can be found here:
> http://bugzilla.kernel.org/show_bug.cgi?id=7689
> comment #64, #65.
> 
> The reason is:
>  - These patches fix a lot weird stuff on all recent
>    HP nc/nx series laptop models.

Well, I'd call that "work around hardware problems in broken HP
laptops". There's HP BIOS bugzilla somewhere, perhaps we should fix it
that way?

>  - The problem with the psmouse thing is, if you booted
>    a broken kernel, rebooting a fixed one will still result
>    in a broken system (things break (or get fixed) on shutdown
>    and survive the reboot).
>    Therefore the patch(es) should get into as much kernels
>    as possible to avoid further confusions on bug reports...

Yes, it is quite nasty problem, but:

1) Fix is non-trivial (>100 lines, which violates -stable rule IIRC)

2) Fix is very disconnected from the problem. "Deinitialize mouse so
that fans work after reboot". WTF?

3) AFAICT it is not a regression.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2007-02-21 19:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 17:08 [PATCH - 2.6.19 -0/2] Backport of psmouse suspend/shutdown cleanups Thomas Renninger
2007-02-21 17:26 ` Dmitry Torokhov
2007-02-22 12:52   ` [PATCH - 2.6.19 -0/1] " Thomas Renninger
2007-02-22 15:02     ` Dmitry Torokhov
2007-02-26 14:21       ` Thomas Renninger
2007-02-26 14:34         ` Dmitry Torokhov
2007-02-28 16:46           ` Thomas Renninger
2007-02-21 19:52 ` Pavel Machek [this message]
2007-02-21 20:22   ` [PATCH - 2.6.19 -0/2] " Alexey Starikovskiy
2007-02-21 20:59     ` Henrique de Moraes Holschuh
2007-02-21 20:26   ` Rafael J. Wysocki
2007-02-21 20:30   ` Dmitry Torokhov
2007-02-21 20:44     ` Pavel Machek
2007-02-22  0:21 ` [stable] " Greg KH
2007-02-22  0:22   ` Greg KH

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=20070221195203.GF3732@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Stable@kernel.org \
    --cc=dtor@insightbb.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=trenn@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