From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: andersen@codepoet.org
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
John Bradford <john@grabjohn.com>,
Erik van Engelen <Info@vanE.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Errors on 2th ide channel of promise ultra100 tx2
Date: Sat, 28 Feb 2004 16:01:34 +0000 [thread overview]
Message-ID: <1077984093.31248.0.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <20040228012630.GA3074@codepoet.org>
On Sad, 2004-02-28 at 01:26, Erik Andersen wrote:
> > Now I remember why this wasn't applied.
> > It breaks braindamaged HDIO_GETGEO_BIG_RAW ioctl
> > (because changes way drive->cyls is calculated).
> > We workaround-ed it in 2.6 by removing this ioctl. :)
> > I think we really should do the same for 2.4.
>
> I did just that but it was rejected by Alan Cox...
> http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0193.html
You can't go around randomly removing bad ideas during a stable
tree. Sucks but true.
Alan
next prev parent reply other threads:[~2004-02-28 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 10:52 Erik van Engelen
2004-02-27 18:46 ` Marcelo Tosatti
2004-02-27 18:20 ` John Bradford
2004-02-27 19:30 ` Marcelo Tosatti
2004-02-27 19:01 ` Alan Cox
2004-02-27 20:14 ` Bartlomiej Zolnierkiewicz
2004-02-27 22:44 ` Erik Andersen
2004-02-28 1:20 ` Bartlomiej Zolnierkiewicz
2004-02-28 1:26 ` Erik Andersen
2004-02-28 16:01 ` Alan Cox [this message]
2004-02-28 20:25 ` John Bradford
2004-02-27 22:51 ` Marcelo Tosatti
2004-02-28 0:04 ` Bartlomiej Zolnierkiewicz
2004-02-27 22:08 ` Erik Andersen
2004-02-27 19:50 ` Rene Herman
2004-02-28 12:13 ` Erik van Engelen
2004-03-03 8:24 ` Erik van Engelen
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=1077984093.31248.0.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=Info@vanE.nl \
--cc=andersen@codepoet.org \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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
all inboxes | Powered by JetHome®