Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Kumba <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: NPTL support for the kernel
Date: Mon, 21 Mar 2005 17:41:51 -0800	[thread overview]
Message-ID: <423F77DF.2060808@avtrex.com> (raw)
In-Reply-To: <423F7305.2030908@gentoo.org>

Kumba wrote:
> Daniel Jacobowitz wrote:
> 
>>
>> Ping?
>>
> 
> Doesn't this need the glibc side of things to be effective?, or is it 
> testable  w/o that component?

I think the main point is that it should not break existing code.

We need NPTL support in all three of GCC, Linux kernel and glibc before 
it can be tested.  If it doesn't break existing code, I think it should 
go in the kernel so that we have something on which to test gcc and glibc.

Just my $0.02

David Daney.

  reply	other threads:[~2005-03-22  1:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 14:11 NPTL support for the kernel Daniel Jacobowitz
2005-03-21 20:34 ` Daniel Jacobowitz
2005-03-22  1:21   ` Kumba
2005-03-22  1:41     ` David Daney [this message]
2005-03-22  3:21       ` Daniel Jacobowitz

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=423F77DF.2060808@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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