linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Testing IDE-TCQ and Taskfile - doesn't work nicely:)
Date: Sun, 29 Jun 2003 10:14:48 +0200	[thread overview]
Message-ID: <20030629081447.GC29233@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10306281917040.1116-100000@master.linux-ide.org>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

On Sat, 2003-06-28 19:17:53 -0700, Andre Hedrick <andre@linux-ide.org>
wrote in message <Pine.LNX.4.10.10306281917040.1116-100000@master.linux-ide.org>:
> 
> The best rule is to default it off and let the end user enable regardless.
> Thus the default will NEVER encounter the issues seen now.

While I was the one who initially had the "trouble", I was thankful for
having a "Switch It On by Default" option. I don't exactly know what the
patch did to the IDE subsystem (personally I'm not really into IDE...),
but I'd unhide a problem (either my dumb drive/controller setup or a bug
in Linux' IDE code) and so - one more bug down (at least from my point
of view). That's a good thing, IMHO.

This *is* why I'm using 2.5.x - there's actually a chance to easily find
bugs with everybody's hardware:)

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-29  8:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 19:45 Testing IDE-TCQ and Taskfile - doesn't work nicely:) Jan-Benedict Glaw
2003-06-23 21:18 ` Bartlomiej Zolnierkiewicz
2003-06-23 22:19   ` Jan-Benedict Glaw
2003-06-23 23:50   ` Jan-Benedict Glaw
2003-06-24  0:53     ` Bartlomiej Zolnierkiewicz
2003-06-24  6:31       ` Jan-Benedict Glaw
2003-06-24 13:44         ` Bartlomiej Zolnierkiewicz
2003-06-24 22:40           ` Jan-Benedict Glaw
2003-06-24 23:08             ` Bartlomiej Zolnierkiewicz
2003-06-25 18:22               ` SOLVED - " Jan-Benedict Glaw
2003-06-25 18:44                 ` Bartlomiej Zolnierkiewicz
2003-06-25 19:05                   ` Jan-Benedict Glaw
2003-06-25 19:30                     ` Bartlomiej Zolnierkiewicz
2003-06-26  3:21                       ` Zwane Mwaikambo
2003-06-26  5:58                       ` Jan-Benedict Glaw
2003-06-24  8:06   ` Jens Axboe
2003-06-24 14:28   ` Jeff Garzik
2003-06-24 14:47     ` Jens Axboe
2003-06-24 15:39       ` Jeff Garzik
2003-06-29  2:17     ` Andre Hedrick
2003-06-29  8:14       ` Jan-Benedict Glaw [this message]
2003-06-29  9:30         ` Andre Hedrick
2003-06-29 10:45           ` Jan-Benedict Glaw

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=20030629081447.GC29233@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=andre@linux-ide.org \
    --cc=axboe@suse.de \
    --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).