From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac1
Date: Mon, 27 Dec 2004 14:33:20 +0000 [thread overview]
Message-ID: <1104157999.20952.40.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e04122616577e1bd33@mail.gmail.com>
On Llu, 2004-12-27 at 00:57, Bartlomiej Zolnierkiewicz wrote:
> Most of these options are pure braindamage (they were obsoleted to
> verify what is what) and they paper over real bugs in core or host drivers.
>
> What do you need 'serialize' option for?
A whole range of quirky systems, probably in most cases buggy hardware,
BIOS firmware setup bugs and the like but they are there and end users
use them. Its __init code so it is free.
As to real bugs there is probably a good three to six months fixing
needed for the DMA timeout paths having been debugging them, along with
timer/irq races all over the place. I'd rather worry about the fact the
IDE eh code is totally hosed first and realistically needs an ide_eh
thread for error handling akin to the SCSI approach.
>
> > o Fix bogus dma_ naming in the 2.6.10 patch (Alan Cox)
>
> It is on purpose, we really don't need 'ide_' prefix in ide_hwif_t.
> The rest of ide_dma_* functions will lose ide_* prefix over time.
The current code uses
dma_ for DMA variables
ide_dma_ for functions
Its nice clean and logical. I'll consider moving my IDE code over to
your naming when the naming is consistent again (with or without the
ide_).
Alan
next prev parent reply other threads:[~2004-12-27 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 23:31 Linux 2.6.10-ac1 Alan Cox
2004-12-27 0:57 ` Bartlomiej Zolnierkiewicz
2004-12-27 1:25 ` Andreas Steinmetz
2004-12-27 1:40 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:28 ` Alan Cox
2004-12-27 15:46 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:45 ` Ross Biro
2004-12-27 15:38 ` Bartlomiej Zolnierkiewicz
2004-12-27 15:49 ` Andreas Steinmetz
2004-12-27 15:54 ` Bartlomiej Zolnierkiewicz
2004-12-27 16:02 ` Andreas Steinmetz
2004-12-27 16:54 ` Alan Cox
2004-12-27 14:36 ` Rafael J. Wysocki
2004-12-27 14:57 ` Andreas Steinmetz
2004-12-27 14:33 ` Alan Cox [this message]
2004-12-27 20:31 ` Rogério Brito
2004-12-27 20:43 ` Michal Schmidt
2004-12-28 0:45 ` Alan Cox
2004-12-28 2:44 ` Rogério Brito
2004-12-30 4:41 ` Gene Heskett
2004-12-30 5:05 ` Gene Heskett
2004-12-30 23:38 ` Alan Cox
2004-12-31 1:06 ` Gene Heskett
2004-12-31 9:57 ` Jan Dittmer
2004-12-31 12:05 ` Gene Heskett
2004-12-31 12:38 ` Jan Dittmer
2004-12-31 13:18 ` Gene Heskett
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=1104157999.20952.40.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.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 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.