public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Andrew Morton <akpm@digeo.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	ch@murgatroid.com, inaky.perez-gonzalez@intel.com,
	hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.68 FUTEX support should be optional
Date: Thu, 15 May 2003 00:01:47 -0300	[thread overview]
Message-ID: <20030515030147.GK6372@conectiva.com.br> (raw)
In-Reply-To: <20030514183925.67a538fc.akpm@digeo.com>

Em Wed, May 14, 2003 at 06:39:25PM -0700, Andrew Morton escreveu:
> Linus Torvalds <torvalds@transmeta.com> wrote:
> --- 25/init/Kconfig~CONFIG_FUTEX	Wed May 14 12:43:16 2003
> +++ 25-akpm/init/Kconfig	Wed May 14 13:06:15 2003
> @@ -108,8 +108,17 @@ config LOG_BUF_SHIFT
>  		     13 =>  8 KB
>  		     12 =>  4 KB
>  
> +menu "Size reduced kernel"
> +
> +config FUTEX
> +	bool "Futex support"
> +	default y
> +	---help---
> +	Say Y if you want support for Fast Userspace Mutexes (Futexes).
> +	WARNING: disabling futex support will probably cause glibc to fail.
>  endmenu
>  
> +endmenu

Thanks! With this CONFIG_TINY is born :)

- Arnaldo

  parent reply	other threads:[~2003-05-15  2:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 23:33 [PATCH] 2.5.68 FUTEX support should be optional 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 [this message]
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
  -- 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  4:32 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
2003-05-15 18:04         ` Christopher Hoover

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=20030515030147.GK6372@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=akpm@digeo.com \
    --cc=ch@murgatroid.com \
    --cc=hch@infradead.org \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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