public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andreas Steinmetz <ast@domdv.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac1
Date: Mon, 27 Dec 2004 16:46:53 +0100	[thread overview]
Message-ID: <58cb370e04122707465d775090@mail.gmail.com> (raw)
In-Reply-To: <1104157732.20952.35.camel@localhost.localdomain>

On Mon, 27 Dec 2004 14:28:53 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Llu, 2004-12-27 at 01:40, Bartlomiej Zolnierkiewicz wrote:
> > > Do you want to force people to disable the io-apic just because of
> > > option removal? In my case the serialized devices are a disk and a
> > > dvd-rw which is rarely used, so disabling the io-apic is a bad solution.
> >
> > No, I want them to fix the problem - whenever it is - ide or apic code. :)
> 
> Or hardware, or SMM ....
> 
> There are some very complex obscure platform specific funnies that end
> up solved by serialize that I doubt anyone will get to the bottom of
> before all the worlds parallel ATA drives have turned to rust (and/or
> sand).
> 
> It seems the gnome desktop disease[1] is spreading to some kernel
> people. It's all init code, its cheap and it works. Making it automated
> in more cases is great, but you'll never stamp out the need for the
> manual one even if its to do the debug to get the automated case right.
> 
> Alan
> 
> [1] Removing configuration features people need before (if ever)
> providing a working alternative that is automatic.

I use KDE. 8)

Sigh, nothing got removed yet...

  reply	other threads:[~2004-12-27 15:46 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 [this message]
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
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=58cb370e04122707465d775090@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ast@domdv.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox