From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Andrew Morton <akpm@osdl.org>, Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12?
Date: Sat, 4 Jun 2005 17:24:53 +0200 [thread overview]
Message-ID: <200506041724.54558.rjw@sisk.pl> (raw)
In-Reply-To: <398710000.1117895711@[10.10.2.4]>
Hi,
On Saturday, 4 of June 2005 16:35, Martin J. Bligh wrote:
>
> --"Martin J. Bligh" <mbligh@mbligh.org> wrote (on Saturday, June 04, 2005 07:23:59 -0700):
>
> >
> >
> > --Andrew Morton <akpm@osdl.org> wrote (on Friday, June 03, 2005 16:38:43 -0700):
> >
> >> Jeff Garzik <jgarzik@pobox.com> wrote:
> >>>
> >>>
> >>> So... are we gonna see 2.6.12 sometime soon?
> >>>
> >>
> >> Current plan is -rc6 in a few days, 2.6.12 a week after that.
> >>
> >>
> >> My things-to-worry-about folder still has 244 entries. Nobody seems to
> >> care much. Poor me.
> >>
> >> Lots of USB problems, quite a few input problems. fbdev, ACPI, ATAPI. All
> >> the usual suspects.
> >
> > The one that worries me is that my x86_64 box won't boot since -rc3
> > See:
> >
> > http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/regression_matrix.html
> >
> > Note large amount of red in left hand column. Backing out the fusion
> > patches to the previous rev didn't fix it.
>
> Filed bug 4709 to track it.
Well, I have a dual-Opteron box with tg3 (AMD chipset) and -rc5+ run happily on it.
Please let me know if I can help somehow.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-06-04 15:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 22:24 2.6.12? Jeff Garzik
2005-06-03 23:37 ` 2.6.12? Francois Romieu
2005-06-04 8:36 ` 2.6.12? Jeff Garzik
2005-06-04 11:33 ` 2.6.12? Francois Romieu
2005-06-04 20:59 ` 2.6.12? Jeff Garzik
2005-06-03 23:38 ` 2.6.12? Andrew Morton
2005-06-03 23:55 ` 2.6.12? Jeff Garzik
2005-06-04 0:05 ` 2.6.12? Andrew Morton
2005-06-06 10:56 ` 2.6.12? Takashi Iwai
2005-06-04 0:01 ` 2.6.12? Wakko Warner
2005-06-04 0:51 ` 2.6.12? Andrew Morton
2005-06-04 0:03 ` 2.6.12? Benjamin Herrenschmidt
2005-06-04 1:19 ` 2.6.12? Andrew Morton
2005-06-04 0:05 ` 2.6.12? Brice Goglin
2005-06-04 1:21 ` 2.6.12? Andrew Morton
2005-06-07 14:43 ` 2.6.12? Brice Goglin
2005-06-07 15:53 ` 2.6.12? Sylvain Meyer
2005-06-08 8:02 ` 2.6.12? Brice Goglin
2005-06-04 0:34 ` 2.6.12? Dave Jones
2005-06-04 1:50 ` 2.6.12? Dmitry Torokhov
2005-06-04 8:15 ` 2.6.12? Russell King
2005-06-04 9:25 ` 2.6.12? Johannes Stezenbach
2005-06-04 12:25 ` 2.6.12? Michael Krufky
2005-06-04 14:23 ` 2.6.12? Martin J. Bligh
2005-06-04 14:35 ` 2.6.12? Martin J. Bligh
2005-06-04 15:24 ` Rafael J. Wysocki [this message]
2005-06-04 22:11 ` 2.6.12? Andrew Morton
2005-06-05 15:02 ` 2.6.12? Martin J. Bligh
2005-06-07 18:16 ` 2.6.12? Martin J. Bligh
2005-06-07 19:24 ` 2.6.12? Andrew Morton
2005-06-08 12:56 ` 2.6.12? Andi Kleen
2005-06-08 19:47 ` 2.6.12? Martin J. Bligh
2005-06-08 23:04 ` 2.6.12? Martin J. Bligh
2005-06-09 4:44 ` 2.6.12? Martin J. Bligh
2005-06-09 19:45 ` 2.6.12? Martin J. Bligh
2005-06-09 13:41 ` 2.6.12? Andi Kleen
2005-06-06 22:06 ` 2.6.12? Adam Belay
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=200506041724.54558.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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