From: kaz Kojima <kkojima@rr.iij4u.or.jp>
To: drepper@redhat.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: Some SH patches
Date: Tue, 01 Oct 2002 23:54:00 -0000 [thread overview]
Message-ID: <200210020654.g926sGO27079@r-rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Tue, 01 Oct 2002 23:23:33 -0700" <3D9A90E5.20606@redhat.com>
>> I've finally sent a SH TLS patch for binutils to the binutils
>> mailing list. Now it assumes fixed TLS instruction sequences
>> according to Uli's suggestion.
>
> Thanks, I've applied the patch.
Thanks a lot.
> Can you send me at some point an updated version of the TLS description?
http://dodo.nurs.or.jp/~kkojima/gnu-on-sh/tls-sh-memo.txt
is, though it's not so complete.
Regards,
kaz
prev parent reply other threads:[~2002-10-02 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 22:13 kaz Kojima
2002-10-01 23:23 ` Ulrich Drepper
2002-10-01 23:54 ` kaz Kojima [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=200210020654.g926sGO27079@r-rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=drepper@redhat.com \
--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).