public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.68 FUTEX support should be optional
Date: Thu, 15 May 2003 11:16:12 -0700	[thread overview]
Message-ID: <3EC3D96C.3030905@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1030515135628.30631A-100000@gatekeeper.tmr.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bill Davidsen wrote:

> He didn't say static linking he said static library. I assume he meant a
> .a lib instead of a .so lib. One which has elements which are made part of
> the executable instead of being part of a shared library.

And in what way does this not match what I say?  The content of the DSO
and the archive is identical functionality-wise and therefore none of
this ever has any influence on whether futexes are used or not.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+w9ls2ijCOnn/RHQRAsfAAJ9sSbudcXdNSHYAB6ICm/fXWRhuQQCgqmMD
cwxSzwuFEeeS6ACGonakUy8=
=+/L9
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-05-15 18:03 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  4:32 [PATCH] 2.5.68 FUTEX support should be optional Christopher Hoover
2003-05-14  6:14 ` Christoph Hellwig
2003-05-14  6:20   ` Miles Bader
2003-05-14  6:28     ` Christoph Hellwig
2003-05-14  6:32   ` Andrew Morton
2003-05-14  6:35     ` Christoph Hellwig
2003-05-14  7:52   ` Christopher Hoover
2003-05-14 19:19     ` Ulrich Drepper
2003-05-14 19:32       ` Dave Jones
2003-05-14 19:44         ` Ulrich Drepper
2003-05-14 19:50           ` Linus Torvalds
2003-05-14 20:01             ` Andrew Morton
2003-05-14 20:43             ` Davide Libenzi
2003-05-14 20:54               ` H. Peter Anvin
2003-05-14 21:05                 ` Davide Libenzi
2003-05-15  0:58             ` Christopher Hoover
2003-05-15  1:20               ` Linus Torvalds
2003-05-15  2:18                 ` Miles Bader
2003-05-15 16:47       ` Ingo Oeser
2003-05-15 17:45         ` Ulrich Drepper
2003-05-15 18:00           ` Bill Davidsen
2003-05-15 18:16             ` Ulrich Drepper [this message]
2003-05-15 18:04         ` Christopher Hoover
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 22:26 Chuck Ebbert
2003-05-14 22:59 ` Carl-Daniel Hailfinger
2003-05-14 23:33 Perez-Gonzalez, Inaky
2003-05-15  0:41 ` Andrew Morton
2003-05-15  0:52   ` Christopher Hoover
2003-05-15  1:00     ` Linus Torvalds
2003-05-15  1:25       ` Andrew Morton
2003-05-15  1:28         ` Linus Torvalds
2003-05-15  1:39           ` Andrew Morton
2003-05-15  1:42             ` Davide Libenzi
2003-05-15  2:02               ` Christopher Hoover
2003-05-15  2:18                 ` Davide Libenzi
2003-05-15  3:01             ` Arnaldo Carvalho de Melo
2003-05-15  3:45             ` Linus Torvalds
2003-05-15 18:14           ` Bill Davidsen
2003-05-16 21:55       ` Alan Cox
2003-05-17  0:01         ` Valdis.Kletnieks
2003-05-17  2:36           ` Andrew Morton
2003-05-17  9:40         ` Werner Almesberger

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=3EC3D96C.3030905@redhat.com \
    --to=drepper@redhat.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