From: Bill Davidsen <davidsen@tmr.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0-test9
Date: Mon, 27 Oct 2003 23:52:42 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1031027234844.23915A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <3F9DD0A6.1010703@pobox.com>
On Mon, 27 Oct 2003, Jeff Garzik wrote:
> bill davidsen wrote:
> > In article <20031027182141.GH32168@vic20.blipp.com>,
> > Patrik Wallstrom <pawal@blipp.com> wrote:
> >
> > | This patch worked for the Promise-controller:
> > | http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/2.6.0-test9-promise20378.patch
> >
> > If this patch solves the problem, might I hope that it will be
> > considered critical enough a bugfix to get into the mainline? I assume
> > the SATA code added in test9 was intended to work, rather than as a
> > place holder.
>
>
> The above patch solves the 'problem' of a particular PCI id not being
> listed in the driver.
>
> IOW it _adds_ new hardware support.
Sounds unlikely to be considered a fix for a major problem. Thanks for the
info. Also sounds unlikely to be a fix for any similar problem :-(
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-10-28 5:02 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 19:09 Linux 2.6.0-test9 Linus Torvalds
2003-10-25 19:52 ` Marcelo Tosatti
2003-10-25 20:14 ` viro
2003-10-25 22:35 ` Linus Torvalds
2003-10-25 23:45 ` Jose Luis Domingo Lopez
2003-10-26 0:22 ` 2.6.0-test9: selinux compile error with "make O=..." Adrian Bunk
2003-10-26 9:49 ` Sam Ravnborg
2003-10-27 13:40 ` Stephen Smalley
2003-10-27 18:42 ` Sam Ravnborg
2003-10-28 15:10 ` Stephen Smalley
2003-10-26 12:05 ` Linux 2.6.0-test9 Patrik Wallstrom
2003-10-27 18:21 ` Patrik Wallstrom
2003-10-27 22:51 ` bill davidsen
2003-10-28 2:12 ` Jeff Garzik
2003-10-28 4:52 ` Bill Davidsen [this message]
2003-10-26 15:05 ` Linux 2.4 <-> 2.6 compatibility (was: Linux 2.6.0-test9) Matthias Andree
2003-10-26 15:18 ` Linux 2.4 <-> 2.6 compatibility Måns Rullgård
2003-10-27 2:51 ` Matthias Andree
2003-10-26 16:06 ` Jochen Hein
2003-10-26 17:47 ` Fabio Massimo Di Nitto
2003-10-26 18:18 ` Jochen Hein
2003-10-27 16:02 ` Linux 2.6.0-test9 (compile stats) John Cherry
2003-10-26 1:16 Linux 2.6.0-test9 Andries.Brouwer
2003-10-26 3:12 ` OGAWA Hirofumi
2003-10-26 5:48 ` Linus Torvalds
2003-10-27 23:26 ` bill davidsen
2003-10-30 9:20 ` Russell King
2003-10-30 16:44 ` Bill Davidsen
2003-10-30 17:23 ` John Bradford
2003-10-26 10:26 Andries.Brouwer
2003-10-26 10:59 Andries.Brouwer
2003-10-27 23:37 ` bill davidsen
2003-10-26 11:08 Andries.Brouwer
2003-10-26 13:57 ` OGAWA Hirofumi
2003-10-26 15:32 Shane Shrybman
2003-10-26 16:27 ` Marco Roeland
2003-10-26 18:51 P. Christeas
2003-10-27 3:16 ` Andrew Morton
2003-10-26 19:40 Andries.Brouwer
2003-10-27 0:01 ` Andrew Morton
2003-10-27 0:21 ` Linus Torvalds
2003-10-27 0:28 ` Linus Torvalds
2003-10-27 6:43 ` David S. Miller
2003-10-27 19:54 ` kuznet
2003-10-27 19:36 ` kuznet
2003-10-28 0:42 ` Tommy Christensen
2003-10-28 18:25 ` kuznet
2003-10-27 1:48 Andries.Brouwer
2003-10-27 2:10 ` Linus Torvalds
2003-10-27 9:40 ` David S. Miller
2003-10-27 9:47 Mikael Pettersson
2003-10-27 10:58 Andries.Brouwer
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=Pine.LNX.3.96.1031027234844.23915A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=jgarzik@pobox.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;
as well as URLs for NNTP newsgroup(s).