From: Andy Jeffries <lkml@andyjeffries.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HPT372 on KR7A-RAID
Date: Mon, 4 Mar 2002 15:40:07 +0000 [thread overview]
Message-ID: <20020304154007.62716a6c.lkml@andyjeffries.co.uk> (raw)
In-Reply-To: <E16dtBF-0006tG-00@the-village.bc.nu>
In-Reply-To: <20020221091319.37e74cba.lkml@andyjeffries.co.uk> <E16dtBF-0006tG-00@the-village.bc.nu>
On Thu, 21 Feb 2002 13:22:37 +0000 (GMT), Alan Cox
<alan@lxorguk.ukuu.org.uk> wrote:
> > I don't know if this has been fixed in 2.4.17/18, if it has...sorry!
> > :-)
>
> Its fixed in 2.4.18-ac at least, and I think in 2.4.18-rc2. Give that a
> go and check its ok
Hi Alan,
It's not fixed in 2.4.18 (released version).
At least, the array of HPT chipsets doesn't have the 372 entry. Does it
fix it neatly (if the index of the revision is above the array label it as
unknown)?
It doesn't seem to as line 225 in drivers/ide/hpt366.c seems to just use
class_rev as an index in to the chipset_names array (which will bomb out
it it tries to access class_rev=5).
Any chance of getting the earlier patch submitted to the mainstream Kernel
by someone who Linus will listen to ;-) (P.S. Linus, if you're listening
sorry for the aspersion that you ignore patches from people, it's just
that I am a lowly Kernel newbie who you won't know/trust (YET!)).
Cheers,
--
Andy Jeffries
Linux/PHP Programmer
- Windows Crash HOWTO: compile the code below in VC++ and run it!
main (){for(;;){printf("Hung up\t\b\b\b\b\b\b");}}
next prev parent reply other threads:[~2002-03-04 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0202210427050.27301-100000@bugs.home.shadowstar.net>
2002-02-21 9:13 ` Andy Jeffries
2002-02-21 9:46 ` Andy Jeffries
2002-02-21 13:16 ` Andy Jeffries
2002-02-21 13:22 ` Alan Cox
2002-03-04 15:40 ` Andy Jeffries [this message]
2002-03-04 16:51 ` Alan Cox
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=20020304154007.62716a6c.lkml@andyjeffries.co.uk \
--to=lkml@andyjeffries.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®