From: Ralf Baechle <ralf@linux-mips.org>
To: Carsten Langgaard <carstenl@mips.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@linux-mips.org
Subject: Re: memcpy
Date: Thu, 19 Sep 2002 15:31:01 +0200 [thread overview]
Message-ID: <20020919153101.A17133@linux-mips.org> (raw)
In-Reply-To: <3D805119.5A9E3C42@mips.com>; from carstenl@mips.com on Thu, Sep 12, 2002 at 10:32:25AM +0200
On Thu, Sep 12, 2002 at 10:32:25AM +0200, Carsten Langgaard wrote:
> I have found another bug in the 64-bit memcpy function, so I figured it
> was time to use the 32-bit version (as it's more or less are prepared
> for 64-bit).
> With a few fixes the memcpy.S file can now be shared between the 32-bit
> and 64-bit kernel (the only difference is the definition of USE_DOUBLE).
>
> I have attached the patch for arch/mips/lib/memcpy.S and the full file
> for the arch/mips64/lib/memcpy.S
Will apply.
Ralf
PS: Same please as to everybody else - always send patches, never send files.
Even worse, tarballs. Yet worse, compressed stuff. All a waste of time.
prev parent reply other threads:[~2002-09-19 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 8:32 memcpy Carsten Langgaard
2002-09-19 13:31 ` Ralf Baechle [this message]
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=20020919153101.A17133@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=carstenl@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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