From: kaz Kojima <kkojima@rr.iij4u.or.jp>
To: libc-hacker@sources.redhat.com
Subject: Re: SH: optimized memcpy/memset
Date: Tue, 09 Jul 2002 23:50:00 -0000 [thread overview]
Message-ID: <200207100650.g6A6oRN18107@r-rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "09 Jul 2002 23:34:32 -0700" <1026282874.24688.58.camel@myware.mynet>
Ulrich Drepper <drepper@redhat.com> wrote:
> On Fri, 2002-07-05 at 01:18, kaz Kojima wrote:
>
>> This patch gives an optimized memcpy/memset for SH. The original patch
>> was written by Toshiyasu Morita <toshiyasu.morita@hsa.hitachi.com>.
>
> We need an assignment. I don't trust semi-conductor companies
> contributing code without one.
I'll request Morita-san to prepare an assignment for it.
Thanks,
kaz
next prev parent reply other threads:[~2002-07-10 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 1:33 kaz Kojima
2002-07-09 23:33 ` Ulrich Drepper
2002-07-09 23:50 ` kaz Kojima [this message]
2003-01-03 3:57 ` kaz Kojima
2003-01-03 9:59 ` Ulrich Drepper
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=200207100650.g6A6oRN18107@r-rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).