All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: admin@nextframe.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [COMMENTS IDE 2.5] - "idebus=66" in 2.5.8 results in "ide_setup: idebus=66 -- BAD OPTION"
Date: Mon, 15 Apr 2002 10:25:20 +0200	[thread overview]
Message-ID: <3CBA8E70.5010605@evision-ventures.com> (raw)
In-Reply-To: <20020415112332.A181@sexything>

Morten Helgesen wrote:
> Hey Martin (and the rest of you)

> Now, I do not know the reasons for changing the code that handles "idebus=" stuff in ide.c (except from the fact

Should be an off by one error there.

> that it now looks cleaner :) - just thought I should let you know. I do not have the time right now to hunt down
> the bug(?) and cook up a patch, but if you want me to, I`ll do it later today. 

I would love if you could have a look at it...

> One more thing, Martin - I compiled a 2.5.8 with TCQ enabled (yep, I`m aware of the fact that this one is _really_ alpha :), 
> and tested it for, oh ... 10 minutes ... the system gave me all sorts of funny responses - segfaults, 
> "inconsistency in ld.so" and so on ... would you like me to collect 'funnies' and send them to you ? If so, just 
> give me a hint.

Thats mostly Jens stuff...


  reply	other threads:[~2002-04-15  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15  9:23 [COMMENTS IDE 2.5] - "idebus=66" in 2.5.8 results in "ide_setup: idebus=66 -- BAD OPTION" Morten Helgesen
2002-04-15  8:25 ` Martin Dalecki [this message]
2002-04-15  9:34   ` Morten Helgesen
2002-04-15  9:40     ` Jens Axboe
2002-04-15 12:16   ` Morten Helgesen
2002-04-15 11:24     ` Martin Dalecki
2002-04-15 17:20     ` Meelis Roos
2002-04-15 22:04       ` Maxwell Spangler
2002-04-15 22:39         ` Vojtech Pavlik
2002-04-15 22:55         ` Andre Hedrick
2002-04-15 23:43           ` Maxwell Spangler

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=3CBA8E70.5010605@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=admin@nextframe.net \
    --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 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.