From: Kito Cheng <kito.cheng@gmail.com>
To: Newlib <newlib@sourceware.org>,
Kito Cheng <kito.cheng@sifive.com>,
Kito Cheng <kito.cheng@gmail.com>
Cc: Corinna Vinschen <vinschen@redhat.com>
Subject: Re: [PATCH 1/2] RISC-V: NaN should return 0 for finite[f]
Date: Thu, 29 Oct 2020 17:46:44 +0800 [thread overview]
Message-ID: <CA+yXCZBe9VzyJGca4K5=07MRp-YgpOzinGFqih3RdzjHJ3JN1w@mail.gmail.com> (raw)
In-Reply-To: <20201029084141.GT5492@calimero.vinschen.de>
Hi Corinna:
> Sending a cover letter per `git format-patch --cover-letter ...' would
> be nice when sending patch series.
Thanks for your reminder :)
prev parent reply other threads:[~2020-10-29 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 15:41 Kito Cheng
2020-10-28 15:41 ` [PATCH 2/2] RISC-V: Fix wrong including file in s_isinf.c Kito Cheng
2020-10-29 8:41 ` [PATCH 1/2] RISC-V: NaN should return 0 for finite[f] Corinna Vinschen
2020-10-29 9:46 ` Kito Cheng [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='CA+yXCZBe9VzyJGca4K5=07MRp-YgpOzinGFqih3RdzjHJ3JN1w@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=newlib@sourceware.org \
--cc=vinschen@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).