From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: libc-alpha <libc-alpha@sources.redhat.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [PATCH] oldsemaphore fixup for hppa (4/3?)
Date: Sun, 12 Oct 2003 17:35:37 -0400 [thread overview]
Message-ID: <20031012213537.GI23999@systemhalted> (raw)
In-Reply-To: <20031010210438.GI6454@systemhalted>
On Fri, Oct 10, 2003 at 05:04:38PM -0400, Carlos O'Donell wrote:
>
> libc-alpha,
>
> Wrote up the changelogs, reviewed them, and then forgot I had a small
> patch to commit for oldsemaphore. This goes in with the first patch 1/3
> that defines the generic libc changes required for linuxthreads to work
> on HPPA.
>
> Cheers,
> Carlos
> ===
>
> 2003-10-10 Carlos O'Donell <carlos@baldric.uwo.ca>
>
> * linuxthreads/oldsemaphore.c: sem_spinlock in struct old_sem_t
> is an __atomic_lock_t.
Patch has been moved into (1/3, Round 2).
c.
next prev parent reply other threads:[~2003-10-12 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 21:04 [parisc-linux] [PATCH] oldsemaphore fixup for hppa (4/3?) Carlos O'Donell
2003-10-12 21:35 ` Carlos O'Donell
2003-10-12 21:35 ` Carlos O'Donell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 21:04 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=20031012213537.GI23999@systemhalted \
--to=carlos@baldric.uwo.ca \
--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