From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Andrew Morton <akpm@zip.com.au>,
Roberto Nibali <ratz@drugphish.ch>,
linux-kernel@vger.kernel.org
Subject: Re: Question about the ide related ioctl's BLK* in 2.5.7-pre1 kernel
Date: Thu, 14 Mar 2002 07:43:26 -0500 [thread overview]
Message-ID: <3C909AEE.1020401@mandrakesoft.com> (raw)
In-Reply-To: <3C9007F5.1000003@drugphish.ch> <3C900A11.55BA4B32@zip.com.au> <3C90939E.4070409@evision-ventures.com>
Martin Dalecki wrote:
> Andrew Morton wrote:
>
>> Roberto Nibali wrote:
>>
>>> What for are BLKRAGET, BLKFRAGET and BLKSECTGET still needed?
>>
>>
>> They got collaterally damaged in the IDE "cleanup". The patch at
>> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.6/dallocbase-10-readahead.patch
>>
>> resurrects them.
>
>
> This is WRONG. What I did here was just removal of unused code.
> They got obsoleted by the BIO infrastructure changes.
Martin,
Did Andrew really deserve that?
Andrew's patch -implements- those ioctls.
Can our new IDE maintainer please have a little bit more patience and
respect to those who have been hacking the kernel actively for a while?
Andrew certainly has earned our respect... calling changes wrong
without reading them does not.
Jeff
next prev parent reply other threads:[~2002-03-14 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 2:16 Question about the ide related ioctl's BLK* in 2.5.7-pre1 kernel Roberto Nibali
2002-03-14 2:25 ` Andrew Morton
2002-03-14 8:00 ` Roberto Nibali
2002-03-14 8:13 ` Andrew Morton
2002-03-14 12:04 ` Martin Dalecki
2002-03-14 20:04 ` Roberto Nibali
2002-03-18 13:28 ` Martin Dalecki
2002-03-18 13:34 ` Jens Axboe
2002-03-18 13:43 ` Martin Dalecki
2002-03-18 13:51 ` Jens Axboe
2002-03-14 12:12 ` Martin Dalecki
2002-03-14 12:43 ` Jeff Garzik [this message]
2002-03-14 12:51 ` Martin Dalecki
2002-03-14 17:38 ` Andrew Morton
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=3C909AEE.1020401@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=akpm@zip.com.au \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
/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.