mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, ian@ianduggan.net (Ian Duggan)
Cc: rml@tech9.net (Robert Love), linux-kernel@vger.kernel.org (linux kernel)
Subject: Re: 2.4.18 Preempt Freezeups
Date: Fri, 15 Mar 2002 09:43:32 +0100	[thread overview]
Message-ID: <E16lnJE-0000VK-00@starship> (raw)
In-Reply-To: <E16lhBg-0002Yc-00@the-village.bc.nu>
In-Reply-To: <E16lhBg-0002Yc-00@the-village.bc.nu>

On March 15, 2002 03:11 am, Alan Cox wrote:
> > Stock 2.4.18+preempt+mki-adapter+win4lin
> > 	- Very frequent, and also repeatable every time I
> > 		try to start win4lin.
> 
> pre-empt is almost certainly going to break things like win4lin

Or rather, a binary thing like win4lin may break pre-empt, putting
further gentle pressure on the vendor to 'go open'.  You could look
at that as a good thing.

I suppose Netraverse will fix it up and life will go on.

-- 
Daniel

  parent reply	other threads:[~2002-03-15  8:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  1:51 Ian Duggan
2002-03-15  1:54 ` Robert Love
2002-03-15  8:36   ` Ian Duggan
2002-03-15 14:30     ` Alan Cox
2002-03-15 21:36       ` Ian Duggan
2002-03-15 16:11     ` Mikael Pettersson
2002-03-15 14:25   ` Robert Love
2002-03-15 19:11     ` Robert Love
2002-03-16  0:40       ` yodaiken
2002-03-16  1:46         ` Mike Fedyk
2002-03-16  3:12           ` yodaiken
2002-03-17  0:33         ` Daniel Phillips
2002-03-17  1:13           ` yodaiken
2002-03-17  1:14             ` Daniel Phillips
2002-03-17  1:54               ` yodaiken
2002-03-17  2:08                 ` Daniel Phillips
2002-03-17 21:17                 ` Davide Libenzi
2002-03-15  2:11 ` Alan Cox
2002-03-15  8:38   ` Ian Duggan
2002-03-15 14:28     ` Alan Cox
2002-03-16 23:51       ` Daniel Phillips
2002-03-17  3:31         ` Alan Cox
2002-03-17 12:59           ` Dave Jones
2002-03-15  8:43   ` Daniel Phillips [this message]
2002-03-15  8:51   ` David S. Miller

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=E16lnJE-0000VK-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ian@ianduggan.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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®