From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-alpha <libc-alpha@sources.redhat.com>,
parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: [PATCH] linuxthreads for hppa (1/3)
Date: Wed, 15 Oct 2003 01:40:45 -0400 [thread overview]
Message-ID: <20031015054045.GE22495@systemhalted> (raw)
In-Reply-To: <3F8CD774.4040400@redhat.com>
On Tue, Oct 14, 2003 at 10:13:24PM -0700, Ulrich Drepper wrote:
>
> I think I've asked this before:
>
> > Use __LT_INITIALIZER_NOT_ZERO instead of __LT_SPINLOCK_INIT.
>
> Why? No unnecessary changes.
__LT_SPINLOCK_INIT is the value of the structure and used for
initialization e.g. { 1, 1, 1, 1 }. It can no longer be used in a macro
evaluation like "#if __LT_SPINLOCK_INIT". Instead the other macros was
added.
> No unnecessary changes. Leave the code you're not using alone.
> And again.
I made the mistake of adding my STACK_GROWS_UP fixes to this patch set.
If you note I have submitted a "Round 2" set of patches that remove
these changes.
Cheeers,
Carlos.
next prev parent reply other threads:[~2003-10-15 5:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 20:44 [parisc-linux] [PATCH] linuxthreads for hppa (1/3) Carlos O'Donell
2003-10-12 21:33 ` [parisc-linux] [PATCH] linuxthreads for hppa (1/3, Round 2) Carlos O'Donell
2003-10-12 21:33 ` Carlos O'Donell
2003-10-15 5:13 ` [parisc-linux] Re: [PATCH] linuxthreads for hppa (1/3) Ulrich Drepper
2003-10-15 5:40 ` Carlos O'Donell
2003-10-15 5:40 ` Carlos O'Donell [this message]
2003-10-15 5:56 ` Ulrich Drepper
2003-10-15 5:56 ` Ulrich Drepper
2003-10-15 14:26 ` Carlos O'Donell
2003-10-15 14:26 ` Carlos O'Donell
2003-10-15 17:36 ` Ulrich Drepper
2003-10-15 18:33 ` Carlos O'Donell
2003-10-15 18:33 ` Carlos O'Donell
2003-10-15 17:36 ` Ulrich Drepper
2003-10-15 5:13 ` Ulrich Drepper
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=20031015054045.GE22495@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=drepper@redhat.com \
--cc=libc-alpha@sources.redhat.com \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.