From: Ingo Molnar <mingo@elte.hu>
To: David Singleton <dsingleton@mvista.com>
Cc: robustmutexes@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Robust Futex update
Date: Fri, 14 Oct 2005 07:45:22 +0200 [thread overview]
Message-ID: <20051014054522.GA22749@elte.hu> (raw)
In-Reply-To: <434DA382.1050100@mvista.com>
* David Singleton <dsingleton@mvista.com> wrote:
> Index: linux-2.6.13/include/linux/futex.h
> ===================================================================
> --- linux-2.6.13.orig/include/linux/futex.h
> +++ linux-2.6.13/include/linux/futex.h
> @@ -1,8 +1,6 @@
> #ifndef _LINUX_FUTEX_H
> #define _LINUX_FUTEX_H
>
> -#include <linux/fs.h>
> -
> /* Second argument to futex syscall */
>
this chunk broke the build, so i added the #include back. Really, the
robust mutex glibc patches should _NOT_ automatically include the
kernel's futex.h file. If they do so and rely on an installed
kernel-headers package then they are broken. Just copy the file into the
glibc tree and remove the #include line.
Ingo
next prev parent reply other threads:[~2005-10-14 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 0:00 Robust Futex update David Singleton
2005-10-14 5:35 ` Ingo Molnar
2005-10-14 5:45 ` Ingo Molnar [this message]
2005-10-14 17:40 ` Khem Raj
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=20051014054522.GA22749@elte.hu \
--to=mingo@elte.hu \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robustmutexes@lists.osdl.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