public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Ulrich Drepper <drepper@redhat.com>,
	Glibc hackers <libc-hacker@sources.redhat.com>,
	linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: Re: [PATCH] Fix sigevent_t stuff
Date: Sun, 31 Aug 2003 16:12:00 -0000	[thread overview]
Message-ID: <20030831161217.GA10286@linux-mips.org> (raw)
In-Reply-To: <20030831145854.GB23189@linux-mips.org>

On Sun, Aug 31, 2003 at 04:58:54PM +0200, Ralf Baechle wrote:

> below patch fixes a mismatch between glibc and the kernel header's
> definition on MIPS.  Please apply.

Please ignore this patch.  Digging through the history of the missmatch
I came to the conclusion that this fix isn't the right one; I'll send
an updated patch.

  Ralf

  reply	other threads:[~2003-08-31 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 14:59 Ralf Baechle
2003-08-31 16:12 ` Ralf Baechle [this message]
     [not found]   ` <20030831164812.GB766@bogon.ms20.nix>
2003-09-03 12:57     ` More sigevent Ralf Baechle

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=20030831161217.GA10286@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=drepper@redhat.com \
    --cc=jsun@mvista.com \
    --cc=libc-hacker@sources.redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).