Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: linux-mips@linux-mips.org, libc-alpha@sources.redhat.com,
	Dominic Sweetman <dom@mips.com>, Nigel Stephens <nigel@mips.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [patch] glibc 2.3: Memory clobber missing from syscalls
Date: Mon, 18 Oct 2004 07:17:24 +0200	[thread overview]
Message-ID: <m31xfwmwpn.fsf@gromit.moeb> (raw)
In-Reply-To: <Pine.LNX.4.61.0410151318550.8084@perivale.mips.com> (Maciej W. Rozycki's message of "Fri, 15 Oct 2004 13:47:59 +0100 (BST)")

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

"Maciej W. Rozycki" <macro@mips.com> writes:

> Hi,
>
>  It seems nobody at the libc-alpha list is intersted in this fix, so I'm 
> sending it here, so that people do not struggle against weird failures, 
> while a fix is already done.  The fix is needed for the current version of 
> glibc.

Sorry, it took me longer to react than normal - but there is interest,
just not always time to do anything properly.

I've committed your patch after adjusting the copyright years also.

Thanks,
Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2004-10-18  5:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 12:47 [patch] glibc 2.3: Memory clobber missing from syscalls Maciej W. Rozycki
2004-10-18  1:37 ` Atsushi Nemoto
2004-10-20  3:05   ` Maciej W. Rozycki
2004-10-20  3:18     ` Ralf Baechle
2004-10-18  5:17 ` Andreas Jaeger [this message]
2004-10-18 16:08   ` Maciej W. Rozycki

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=m31xfwmwpn.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=dom@mips.com \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --cc=nigel@mips.com \
    /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