public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ronnie Sahlberg" <sahlberg@optushome.com.au>
To: <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.5.6-pre2 IDE cleanup 16
Date: Thu, 7 Mar 2002 00:46:52 +1100	[thread overview]
Message-ID: <007501c1c519$fe289010$0901010a@C5043436> (raw)

>MD> 2. It convinced me that the current task-file interface in linux
>MD> is inadequate. So Alan please bear with me if your CF format
>MD> microdrive will have to not wakeup properly for some time...
>MD> The current mess will just have to go before something more
>MD> adequate can go in.
>
>Why not keep the existing taskfile implementation in until you complete the
>elegant implementation?

seriously, ide has always been a joke for anyone serious in storage capacity
or robustness. so what.

if you were serious in using ide drives you would have been using external
patches for quite a while anyway. nothings changed.
Well, nothing, except that now, that there will be a much higher percentage
of users that relies on external patches for ide to be useful
or work at all

time for someone actually has a clue on how modern ide drives works to have
a say for a change...?



             reply	other threads:[~2002-03-06 14:15 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 13:46 Ronnie Sahlberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-13 15:55 [PATCH] 2.5.6-pre2 IDE cleanup 16 Rick A. Hohensee
2002-03-05  7:54 [PATCH] per-cpu areas Rusty Russell
2002-03-05 10:51 ` [PATCH] 2.5.6-pre2 IDE cleanup 16 Martin Dalecki
2002-03-05 11:07   ` Zwane Mwaikambo
2002-03-05 11:28     ` Jens Axboe
2002-03-05 11:54       ` Martin Dalecki
2002-03-05 12:04         ` Jens Axboe
2002-03-05 12:09           ` Martin Dalecki
2002-03-06  0:33         ` Alan Cox
2002-03-06  9:51           ` Martin Dalecki
2002-03-05 11:48     ` Martin Dalecki
2002-03-06  0:34       ` Alan Cox
2002-03-05 12:36     ` Anton Altaparmakov
2002-03-05 12:36       ` Martin Dalecki
2002-03-05 12:35         ` Zwane Mwaikambo
2002-03-06  0:28         ` Alan Cox
2002-03-05 12:47       ` Anton Altaparmakov
2002-03-05 12:52         ` Martin Dalecki
2002-03-06  1:40           ` Alan Cox
2002-03-06  8:56             ` Zwane Mwaikambo
2002-03-06  9:43             ` Martin Dalecki
2002-03-06  0:27       ` Alan Cox
2002-03-06 10:15         ` Martin Dalecki
2002-03-05 11:37   ` Arjan van de Ven
2002-03-05 11:51     ` Martin Dalecki
2002-03-05 21:19     ` Vojtech Pavlik
2002-03-05 21:42       ` Jeff Garzik
2002-03-05 21:46         ` Vojtech Pavlik
2002-03-06  9:19           ` Martin Dalecki
2002-03-06  1:08       ` Alan Cox
2002-03-06  9:45         ` Martin Dalecki
2002-03-06  0:41   ` Alan Cox
2002-03-06  9:15     ` benh
2002-03-06 11:07       ` Martin Dalecki
2002-03-06 11:12         ` Zwane Mwaikambo
2002-03-06 11:59           ` Martin Dalecki
2002-03-06 12:02         ` Meelis Roos
2002-03-06 12:11           ` Martin Dalecki
2002-03-06 16:01         ` Bill Davidsen
2002-03-06 20:36           ` Linus Torvalds
2002-03-06 17:00         ` benh
2002-03-06  9:49     ` Martin Dalecki

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='007501c1c519$fe289010$0901010a@C5043436' \
    --to=sahlberg@optushome.com.au \
    --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