From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Ross Biro <ross.biro@gmail.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac1
Date: Mon, 27 Dec 2004 16:38:30 +0100 [thread overview]
Message-ID: <58cb370e0412270738fbc045c@mail.gmail.com> (raw)
In-Reply-To: <8783be660412270645717b89d1@mail.gmail.com>
On Mon, 27 Dec 2004 09:45:54 -0500, Ross Biro <ross.biro@gmail.com> wrote:
> On Mon, 27 Dec 2004 02:40:45 +0100, Bartlomiej Zolnierkiewicz
> <bzolnier@gmail.com> wrote:
> > On Mon, 27 Dec 2004 02:25:50 +0100, Andreas Steinmetz <ast@domdv.de> wrote:
> > > Bartlomiej Zolnierkiewicz wrote:
> > > > What do you need 'serialize' option for?
> >
> > No, I want them to fix the problem - whenever it is - ide or apic code. :)
>
> And what do you want them to do when the problem is in hardware?
Workaround it if it is possible. If this is really a unfixable hardware problem
(hard to believe - other OS-es would be also bitten by the issue) shouldn't it
be workaround differently anyway by something like "ide=serialize_all" (which
is much saner from IDE POV than "idex=serialize") ?
The reason I want to remove some of IDE options is that otherwise I have to
add ~ 200 lines of ugly code for storing them in the temporary buffer (part of
dynamic ide_hwifs[] patch) and it still is wrong...
IDE option -> IDE core -> IDE host driver
while it really should be
IDE option -> IDE host driver
Bartlomiej
next prev parent reply other threads:[~2004-12-27 15:39 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 [this message]
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
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=58cb370e0412270738fbc045c@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.biro@gmail.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 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.