public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Matt Mackall <mpm@selenic.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: 2.6.21-mm2: ACPI exception on resume
Date: Wed, 23 May 2007 09:51:00 -0300	[thread overview]
Message-ID: <20070523125100.GA826@khazad-dum.debian.net> (raw)
In-Reply-To: <2c0942db0705222141se133553re06370476d436b12@mail.gmail.com>

On Tue, 22 May 2007, Ray Lee wrote:
> On 5/22/07, Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> >> I shouldn't have to upgrade my BIOS to work with a new kernel any more
> >> than I should have to upgrade my browser.
> >
> >We don't agree there, as you are not talking about a stable kernel series.
> 
> Ah, so you're planning on submitting these patches for 2.7 then? 2.6
> is perpetually stable. Matt is quite correct; feel free to ask for
> clarifications from Linus et al if you need guidance.

2.6.x.y is stable.  2.6.x is not by any reasonably strict definition of
stable.  Unless you can explain how the stuff that went in 2.6.21 could be
added to a stable series kernel, do not even bother replying.

And for the record, the patches are NOT mine, but since I am the one usually
dealing directly with thinkpad firmware, I jumped in to help debug things as
a thinkpad firmware was *probably* to blame.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2007-05-23 12:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19 16:57 2.6.21-mm2: ACPI exception on resume Matt Mackall
2007-05-19 18:24 ` Rafael J. Wysocki
2007-05-19 22:40   ` Matt Mackall
2007-05-19 23:05     ` Rafael J. Wysocki
2007-05-19 20:45 ` Henrique de Moraes Holschuh
2007-05-19 22:38   ` Matt Mackall
2007-05-20  3:52     ` Henrique de Moraes Holschuh
2007-05-21 22:23       ` Matt Mackall
2007-05-21 23:03         ` Henrique de Moraes Holschuh
2007-05-22 22:45           ` Matt Mackall
2007-05-23  0:19             ` Henrique de Moraes Holschuh
2007-05-23  1:48               ` Matt Mackall
2007-05-23  4:19                 ` Henrique de Moraes Holschuh
2007-05-23  4:41                   ` Ray Lee
2007-05-23 12:51                     ` Henrique de Moraes Holschuh [this message]
2007-05-23 22:50                       ` Ray Lee
2007-05-24  0:28                         ` Henrique de Moraes Holschuh
2007-05-24  1:37                           ` Ray Lee
2007-05-27 21:02                       ` Pavel Machek
2007-05-23  8:57                 ` Rafael J. Wysocki
2007-05-23 17:13                   ` Henrique de Moraes Holschuh
2007-05-23 17:48                     ` Matt Mackall
2007-05-23 20:56                       ` Rafael J. Wysocki
2007-05-23 21:15                         ` Matt Mackall

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=20070523125100.GA826@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=ray-lk@madrabbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox