Linux PARISC architecture development
 help / color / mirror / Atom feed
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 10:26:49 -0400	[thread overview]
Message-ID: <20031015142648.GF22495@systemhalted> (raw)
In-Reply-To: <3F8CE195.2090106@redhat.com>

Ulrich,

> - -# if __LT_SPINLOCK_INIT != 0
> - -  __pthread_handles[0].h_lock = __LOCK_INITIALIZER;
> - -  __pthread_handles[1].h_lock = __LOCK_INITIALIZER;
> +# ifdef __LT_INITIALIZER_NOT_ZERO
> +  __pthread_handles[0].h_lock = __LOCK_ALT_INITIALIZER;
> +  __pthread_handles[1].h_lock = __LOCK_ALT_INITIALIZER;
> 
> part is what I meant.  There is no reason to change the name.

How do you propose it be handled? All arches define __LT_SPINLOCK_INIT
and thus it cannot be used to distinguish between the two cases. Why do
we distinguish between the two cases? Because a structure as an
initializer has two different assignments cases, one in which it is
named and one which it is not.
 
> Look at your change, no changes of code which are not needed.  Clean up
> the patches to follow the coding standard, preprocessor indentation, etc
> etc.

I do apologize for the STACK_GROWS_UP patches being included, and
rightly so I removed them. Thank you for applying those patches.

I will go over my patches again for coding standard, preprocessor
indentation and other grievences. In most cases I have tried to follow 
the standard.

Cheers,
Carlos.

  reply	other threads:[~2003-10-15 14:30 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:13 ` Ulrich Drepper
2003-10-15  5:40   ` Carlos O'Donell
2003-10-15  5:56     ` Ulrich Drepper
2003-10-15 14:26       ` Carlos O'Donell [this message]
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 14:26       ` Carlos O'Donell
2003-10-15  5:56     ` Ulrich Drepper
2003-10-15  5:40   ` Carlos O'Donell

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=20031015142648.GF22495@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox