From: Christoph Hellwig <hch@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ulrich Drepper <drepper@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] futex patches, futex-2.5.69-A2
Date: Tue, 20 May 2003 15:08:26 +0100 [thread overview]
Message-ID: <20030520150826.A18282@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0305201412260.10571-100000@localhost.localdomain>; from mingo@elte.hu on Tue, May 20, 2003 at 02:56:42PM +0200
On Tue, May 20, 2003 at 02:56:42PM +0200, Ingo Molnar wrote:
> it's not vendor braindamage.
I didn't sayd sys_futex is vendor braindamage. The problem is that vendors
think they need to put all the unstable features into their release tree.
There's a reaaon those aren';t in the released stable kernels.
> you dont understand, do you? There are very valid and perfectly working
> glibc installations [and maybe NGPT installations, futex users, etc.] out
> there that will break if you remove sys_futex(). No amount of rpm hacking
> will fix them up.
And they'll break if you run _any_ released stable kernel, so what?
Let the vendors fix the mess they introduced by backporting unstable features
instead of burdening it up on mainline.
next prev parent reply other threads:[~2003-05-20 13:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 9:31 [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Ingo Molnar
2003-05-19 10:10 ` Christoph Hellwig
2003-05-19 10:16 ` Ingo Molnar
2003-05-19 11:49 ` Christoph Hellwig
2003-05-19 12:33 ` [patch] futex API cleanups, futex-api-cleanup-2.5.69-A2 Ingo Molnar
2003-05-19 12:51 ` Ingo Molnar
2003-05-19 14:47 ` bert hubert
2003-05-19 16:02 ` Ingo Molnar
2003-05-19 15:18 ` Linus Torvalds
2003-05-19 16:06 ` Ingo Molnar
2003-05-19 23:33 ` Jamie Lokier
2003-05-20 0:39 ` Rusty Russell
2003-05-20 1:14 ` Davide Libenzi
2003-05-20 1:44 ` Jamie Lokier
2003-05-20 16:54 ` Davide Libenzi
2003-05-20 17:59 ` Jamie Lokier
2003-05-21 23:56 ` Davide Libenzi
2003-05-20 1:50 ` Jamie Lokier
2003-05-20 0:15 ` Rusty Russell
2003-05-20 0:08 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Rusty Russell
2003-05-20 0:31 ` Valdis.Kletnieks
2003-05-19 10:23 ` Andrew Morton
2003-05-19 10:30 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D4 Ingo Molnar
2003-05-20 0:04 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Rusty Russell
2003-05-20 0:40 ` Ulrich Drepper
2003-05-20 1:46 ` Rusty Russell
2003-05-20 2:11 ` Ulrich Drepper
2003-05-20 6:27 ` Ingo Molnar
2003-05-20 6:56 ` Christoph Hellwig
2003-05-20 8:57 ` Rusty Russell
2003-05-20 9:03 ` Ingo Molnar
2003-05-20 9:51 ` Christoph Hellwig
2003-05-20 12:56 ` [patch] futex patches, futex-2.5.69-A2 Ingo Molnar
2003-05-20 14:08 ` Christoph Hellwig [this message]
2003-05-20 16:02 ` Ingo Molnar
2003-05-20 19:55 ` Christoph Hellwig
2003-05-21 5:06 ` Martin Schlemmer
2003-05-21 6:31 ` Christoph Hellwig
2003-05-20 15:46 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Linus Torvalds
2003-05-20 9:12 ` Ingo Oeser
2003-05-20 15:41 ` Linus Torvalds
2003-05-20 8:55 ` Rusty Russell
2003-05-20 6:19 ` Ingo Molnar
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=20030520150826.A18282@infradead.org \
--to=hch@infradead.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--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