The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alex Riesen <fork0@users.sourceforge.net>
To: inaky.perez-gonzalez@intel.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH] FUSYN 1/10: documentation files
Date: Wed, 3 Dec 2003 19:01:01 +0100	[thread overview]
Message-ID: <20031203180101.GA1748@steel.home> (raw)

> +I am calling these things FUSYNs to distinguish them from the original
> +futexes they base on, as they behave kind of different (the naming
> +sucks, you are welcome to suggest new names).

FUSYNC [fu'sink]


             reply	other threads:[~2003-12-03 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 18:01 Alex Riesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14 22:49 [RFC/PATCH] FUSYN Realtime & Robust mutexes for Linux try 2.1 inaky.perez-gonzalez
2004-01-14 22:49 ` [RFC/PATCH] FUSYN 1/10: documentation files inaky.perez-gonzalez
2003-12-03  8:51 [RFC/PATCH] FUSYN Realtime & Robust mutexes for Linux try 2 inaky.perez-gonzalez
2003-12-03  8:51 ` [RFC/PATCH] FUSYN 1/10: documentation files inaky.perez-gonzalez

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=20031203180101.GA1748@steel.home \
    --to=fork0@users.sourceforge.net \
    --cc=inaky.perez-gonzalez@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox