From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Olaf Hering <olaf@aepfle.de>
Cc: linuxppc-dev@ozlabs.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc5
Date: Thu, 5 Jun 2008 13:42:22 +0100 [thread overview]
Message-ID: <20080605134222.76e117a4@core> (raw)
In-Reply-To: <20080605112436.GA4533@aepfle.de>
On Thu, 5 Jun 2008 13:24:36 +0200
Olaf Hering <olaf@aepfle.de> wrote:
> On Wed, Jun 04, Linus Torvalds wrote:
>
> > Another week, another batch of mostly pretty small fixes. Hopefully the
> > regression list is shrinking, and we've fixed at least a couple of the
> > oopses on Arjan's list.
>
> SATA on a dualcore G5 is broken, it happend between
See the patch I just posted to Nick/Jeff should fix it. I always said
ata_sff_check_status() was asking for trouble as a name and neither I nor
Jeff nor Linus noticed the bug...
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Olaf Hering <olaf@aepfle.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linuxppc-dev@ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc5
Date: Thu, 5 Jun 2008 13:42:22 +0100 [thread overview]
Message-ID: <20080605134222.76e117a4@core> (raw)
In-Reply-To: <20080605112436.GA4533@aepfle.de>
On Thu, 5 Jun 2008 13:24:36 +0200
Olaf Hering <olaf@aepfle.de> wrote:
> On Wed, Jun 04, Linus Torvalds wrote:
>
> > Another week, another batch of mostly pretty small fixes. Hopefully the
> > regression list is shrinking, and we've fixed at least a couple of the
> > oopses on Arjan's list.
>
> SATA on a dualcore G5 is broken, it happend between
See the patch I just posted to Nick/Jeff should fix it. I always said
ata_sff_check_status() was asking for trouble as a name and neither I nor
Jeff nor Linus noticed the bug...
next prev parent reply other threads:[~2008-06-05 12:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 3:36 Linux 2.6.26-rc5 Linus Torvalds
2008-06-05 11:24 ` Olaf Hering
2008-06-05 12:09 ` Linux 2.6.26-rc5 (G5 SATA broken) Hugh Dickins
2008-06-05 12:09 ` Hugh Dickins
2008-06-05 12:54 ` Alan Cox
2008-06-05 12:54 ` Alan Cox
2008-06-05 13:44 ` [PATCH] libata: fix G5 SATA broken on -rc5 Hugh Dickins
2008-06-05 13:44 ` Hugh Dickins
2008-06-05 14:45 ` Olaf Hering
2008-06-05 14:45 ` Olaf Hering
2008-06-06 4:36 ` Linux 2.6.26-rc5 (G5 SATA broken) Benjamin Herrenschmidt
2008-06-06 4:36 ` Benjamin Herrenschmidt
2008-06-05 12:42 ` Alan Cox [this message]
2008-06-05 12:42 ` Linux 2.6.26-rc5 Alan Cox
2008-06-05 13:03 ` Alejandro Riveira Fernández
2008-06-05 14:54 ` Linus Torvalds
2008-06-05 15:12 ` Bjorn Helgaas
2008-06-05 16:12 ` Bjorn Helgaas
2008-06-05 16:19 ` Linus Torvalds
2008-06-05 16:32 ` Bjorn Helgaas
2008-06-05 14:43 ` Ben Dooks
2008-06-06 18:35 ` Linus Torvalds
2008-06-10 12:57 ` ACPI pull for 2.6.26? Adrian Bunk
2008-06-10 15:23 ` Len Brown
2008-06-10 15:39 ` Adrian Bunk
2008-06-05 14:47 ` Linux 2.6.26-rc5 Alex Romosan
2008-06-07 19:44 ` Jesper Krogh
2008-06-07 21:50 ` Frans Pop
2008-06-09 3:39 ` Bjorn Helgaas
2008-06-09 10:01 ` Frans Pop
2008-06-07 19:52 ` Jesper Krogh
-- strict thread matches above, loose matches on Subject: below --
2008-06-05 15:04 Lior Dotan
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=20080605134222.76e117a4@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
--cc=torvalds@linux-foundation.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.