From: Lee Revell <rlrevell@joe-job.com>
To: Joshua Hudson <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc5: known regressions [TP 600X S3, vanilla DSDT]
Date: Sat, 20 May 2006 23:53:40 -0400 [thread overview]
Message-ID: <1148183621.20472.57.camel@mindpipe> (raw)
In-Reply-To: <bda6d13a0605201830x1aa4cb81m95a52bb91ab51ebb@mail.gmail.com>
On Sat, 2006-05-20 at 18:30 -0700, Joshua Hudson wrote:
> On 5/20/06, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> wrote:
> > Please try kernel 2.6.16.17 (just released). It has the SMBus fix which
> > may fix resume and fan behaviour.
>
> Am I the only person who read that as 2.6.17 the first time around?
I think it's evidence that the -stable process is working brilliantly.
We have 17 point releases worth of bug fixes that would not have been
available under the previous model.
Lee
next prev parent reply other threads:[~2006-05-21 3:53 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 9:04 2.6.16-rc5: known regressions Yu, Luming
2006-03-03 2:59 ` Sanjoy Mahajan
2006-03-03 16:51 ` Matthew Garrett
2006-03-03 21:04 ` Sanjoy Mahajan
2006-03-10 5:26 ` 2.6.16-rc5: known regressions [TP 600X S3, vanilla DSDT] Sanjoy Mahajan
2006-05-19 13:44 ` Thomas Renninger
2006-05-21 0:12 ` Sanjoy Mahajan
2006-05-21 0:40 ` Carl-Daniel Hailfinger
2006-05-21 1:30 ` Joshua Hudson
2006-05-21 3:53 ` Lee Revell [this message]
2006-05-22 9:55 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-03-10 6:12 Yu, Luming
2006-03-10 6:27 ` Sanjoy Mahajan
2006-03-10 6:46 Yu, Luming
2006-03-10 13:27 ` Sanjoy Mahajan
2006-03-10 13:36 ` Sanjoy Mahajan
2006-03-13 2:00 Yu, Luming
2006-03-13 4:38 ` Sanjoy Mahajan
2006-03-13 4:51 Yu, Luming
2006-03-13 7:28 ` Sanjoy Mahajan
2006-03-13 8:35 Yu, Luming
2006-03-13 15:21 ` Sanjoy Mahajan
2006-03-14 1:48 Yu, Luming
2006-03-14 8:28 ` Sanjoy Mahajan
2006-03-15 1:46 Yu, Luming
2006-03-15 5:40 ` Sanjoy Mahajan
2006-03-15 5:57 ` Sanjoy Mahajan
2006-03-15 6:16 Yu, Luming
2006-03-15 6:35 ` Sanjoy Mahajan
2006-03-15 6:25 Yu, Luming
2006-03-15 6:47 Yu, Luming
2006-03-15 7:06 ` Sanjoy Mahajan
2006-03-15 8:02 Yu, Luming
2006-03-16 0:03 ` Sanjoy Mahajan
2006-03-16 5:47 ` Sanjoy Mahajan
2006-03-16 6:46 ` Sanjoy Mahajan
2006-03-16 6:41 Yu, Luming
2006-03-16 6:54 ` Sanjoy Mahajan
2006-03-16 7:14 ` Sanjoy Mahajan
2006-03-16 7:28 Yu, Luming
2006-03-16 7:57 ` Sanjoy Mahajan
2006-03-16 8:18 Yu, Luming
2006-03-16 15:15 ` Sanjoy Mahajan
2006-03-17 1:17 Yu, Luming
2006-03-17 6:28 ` Sanjoy Mahajan
2006-03-17 6:57 Yu, Luming
2006-03-17 7:11 ` Sanjoy Mahajan
2006-03-17 7:32 ` Sanjoy Mahajan
2006-03-17 7:50 Yu, Luming
2006-03-17 18:43 ` Sanjoy Mahajan
2006-03-18 2:02 Yu, Luming
2006-03-18 7:23 ` Sanjoy Mahajan
2006-03-18 13:24 Yu, Luming
2006-03-18 14:37 ` Sanjoy Mahajan
2006-03-18 15:10 Yu, Luming
2006-03-18 15:48 ` Sanjoy Mahajan
2006-03-18 15:58 Yu, Luming
2006-03-18 16:27 ` Sanjoy Mahajan
2006-03-18 16:37 Yu, Luming
2006-03-18 17:03 ` Sanjoy Mahajan
2006-03-18 17:08 Yu, Luming
2006-03-18 20:12 ` Sanjoy Mahajan
2006-03-19 4:12 Yu, Luming
2006-03-19 14:33 ` Sanjoy Mahajan
2006-03-20 6:39 ` Sanjoy Mahajan
2006-03-21 1:38 Yu, Luming
2006-03-21 7:27 ` Sanjoy Mahajan
2006-03-21 8:47 ` Sanjoy Mahajan
2006-03-21 9:11 Yu, Luming
2006-03-21 20:37 ` Sanjoy Mahajan
2006-03-21 22:09 ` Sanjoy Mahajan
2006-03-22 1:30 Yu, Luming
2006-03-22 4:35 ` Sanjoy Mahajan
2006-03-22 7:15 ` Sanjoy Mahajan
2006-03-22 1:34 Yu, Luming
2006-03-22 7:00 ` Sanjoy Mahajan
2006-03-22 4:58 Yu, Luming
2006-03-22 5:13 ` Sanjoy Mahajan
2006-03-24 1:17 ` Sanjoy Mahajan
2006-03-22 7:28 Yu, Luming
2006-03-22 14:16 ` Sanjoy Mahajan
2006-03-23 4:46 Yu, Luming
2006-03-23 6:25 ` Sanjoy Mahajan
2006-03-23 9:10 Yu, Luming
2006-03-23 19:19 ` Sanjoy Mahajan
2006-03-24 1:31 Yu, Luming
2006-04-04 6:49 ` Sanjoy Mahajan
2006-04-05 3:03 Yu, Luming
2006-05-23 13:29 Yu, Luming
2006-05-23 17:12 ` Sanjoy Mahajan
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=1148183621.20472.57.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=joshudson@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox