From: Andre Tomt <andre@tomt.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-rc4 - pls test (and no more patches)
Date: Mon, 11 Oct 2004 20:22:22 +0200 [thread overview]
Message-ID: <416ACF5E.80407@tomt.net> (raw)
In-Reply-To: <1097507381.2029.40.camel@mulgrave>
James Bottomley wrote:
> On Mon, 2004-10-11 at 10:02, Linus Torvalds wrote:
>>On Mon, 11 Oct 2004, Andre Tomt wrote:
>>>"[PATCH]: megaraid 2.20.4: Fixes a data corruption bug"
>>
>>I think that one is already in the SCSI BK tree, just not pushed to me.
>>Perhaps because the tree contains other less important patches that James
>>doesn't think are worthy yet.. James? Should I just take the small
>>megaraid patch directly (and leave the compat ioctl cleanups etc to you)?
>
> I have no objections. However, I was planning on pushing it through the
> SCSI tree because it's in the new megaraid driver which is experimental
> at the moment (the old megaraid driver is still in and still
> selectable). It's been in -mm for a few days now with no ill effects, I
> think, but I'm not sure how many megaraid owners have actually tested
> it.
I've been running 2.20.3.1 + the data corruption bug fix on megaraids
ranging from low-end SATA adapters to the u320scsi ones for a while on a
2.6.8 based kernel, nothing have blown up yet. The old 2.20.3.1 without
the fix have been holding up too though - however having a known data
corruption bug lingering doesn't feel so good :-)
next prev parent reply other threads:[~2004-10-11 18:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 3:22 Linux 2.6.9-rc4 - pls test (and no more patches) Linus Torvalds
2004-10-11 7:07 ` Gene Heskett
2004-10-11 7:23 ` via-velocity heads up (was (Re: Linux 2.6.9-rc4 - pls test (and no more patches)) Francois Romieu
2004-10-11 13:32 ` Daniel Andersen
2004-10-11 16:53 ` Jerone Young
2004-10-11 9:07 ` Linux 2.6.9-rc4 - pls test (and no more patches) Brice Goglin
2004-10-11 14:57 ` Linus Torvalds
2004-10-11 20:22 ` Kjartan Maraas
2004-10-11 9:35 ` Andre Tomt
2004-10-11 15:02 ` Linus Torvalds
2004-10-11 15:09 ` James Bottomley
2004-10-11 18:22 ` Andre Tomt [this message]
2004-10-11 19:29 ` James Bottomley
2004-10-11 23:35 ` Linus Torvalds
2004-10-12 1:01 ` Lee Revell
2004-10-12 4:02 ` William Lee Irwin III
2004-10-12 6:57 ` Jesper Juhl
2004-10-11 21:37 ` Chris Ricker
2004-10-11 9:54 ` Nick Piggin
2004-10-11 15:17 ` Linus Torvalds
2004-10-11 15:25 ` Linus Torvalds
2004-10-12 0:11 ` Nick Piggin
2004-10-11 23:48 ` Nick Piggin
2004-10-12 6:00 ` Barry K. Nathan
2004-10-11 15:48 ` Linux 2.6.9-rc4 (compile stats) John Cherry
2004-10-11 15:51 ` John Cherry
2004-10-11 16:24 ` [patch] 2.6.9-rc4: SCSI qla2xxx gcc 3.4 compile errors Adrian Bunk
2004-10-11 16:28 ` James Bottomley
2004-10-11 16:35 ` Adrian Bunk
2004-10-11 17:05 ` James Bottomley
2004-10-11 22:04 ` Linux 2.6.9-rc4 - pls test (and no more patches) Tom Rini
2004-10-11 23:23 ` Tom Rini
2004-10-12 8:05 ` Matthias Andree
2004-10-12 9:09 ` [PATCH] tcp_output.c: tcp_set_skb_tso_factor ---> tcp_set_skb_tso_segs [Was: Re: Linux 2.6.9-rc4 - pls test (and no more patches)] Sami Farin
2004-10-11 16:07 Linux 2.6.9-rc4 - pls test (and no more patches) Yu, Luming
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=416ACF5E.80407@tomt.net \
--to=andre@tomt.net \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.