From: Jens Axboe <axboe@suse.de>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.6-pre2 IDE cleanup 16
Date: Tue, 5 Mar 2002 13:04:26 +0100 [thread overview]
Message-ID: <20020305120426.GC14996@suse.de> (raw)
In-Reply-To: <3C84A34E.6060708@evision-ventures.com> <Pine.LNX.4.44.0203051307080.12437-100000@netfinity.realnet.co.sz> <20020305112843.GE716@suse.de> <3C84B1FB.2050003@evision-ventures.com>
In-Reply-To: <3C84B1FB.2050003@evision-ventures.com>
On Tue, Mar 05 2002, Martin Dalecki wrote:
> Jens Axboe wrote:
> >On Tue, Mar 05 2002, Zwane Mwaikambo wrote:
> >
> >>On Tue, 5 Mar 2002, Martin Dalecki wrote:
> >>
> >>
> >>>- Disable configuration of the task file stuff. It is going to go away
> >>> and will be replaced by a truly abstract interface based on
> >>> functionality and *not* direct mess-up of hardware.
> >>>
> >>Could you elaborate just a tad on that.
> >>
> >
> >While the taskfile interface is very down-to-basics and a bit extreme
> >in one end, it's also very useful for eg vendors doing testing and
> >certification. So in that respect it's pretty powerful, I hope Martin
> >isn't just planning a stripped down interface akin to what we have in
> >2.4 and earlier.
>
> No quite my plan is:
>
> 1. Rip it off.
> 2. Reimplement stuff if and only if someone really shows pressure
> for using it.
Someone has, I'll forward you the stuff.
> The "command parsing" excess is certainly going to go.
Agree
--
Jens Axboe
next prev parent reply other threads:[~2002-03-05 12:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 13:46 Ronnie Sahlberg
2002-03-13 15:55 Rick A. Hohensee
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=20020305120426.GC14996@suse.de \
--to=axboe@suse.de \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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