public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: wwp <subscript@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: low latency & preemtible kernels
Date: Wed, 27 Feb 2002 08:53:27 +0100	[thread overview]
Message-ID: <20020227085327.74a2ed0c.subscript@free.fr> (raw)
In-Reply-To: <200202261918.53190.Dieter.Nuetzel@hamburg.de>
In-Reply-To: <200202261918.53190.Dieter.Nuetzel@hamburg.de>

Hi all,


Okay, I would like to thank everyone who has answered my newbie
question! It has helped, making the differences between lo-latency
and preempt patches more clear to me :-)


Regards

-- 
wwp

  parent reply	other threads:[~2002-02-27  7:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 18:18 low latency & preemtible kernels Dieter Nützel
2002-02-26 22:55 ` J.A. Magallon
2002-02-26 23:12   ` wwp
2002-02-26 23:27     ` J.A. Magallon
2002-02-26 23:30   ` Dieter Nützel
2002-02-27  7:53 ` wwp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-26 13:11 wwp
2002-02-27  2:32 ` george anzinger
2002-02-27  3:01   ` Andrew Morton

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=20020227085327.74a2ed0c.subscript@free.fr \
    --to=subscript@free.fr \
    --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