From: Jim Wilson <jimw@sifive.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: Xing GUO <higuoxing@gmail.com>, Kito Cheng <kito.cheng@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] RISC-V: Fix -march option parsing when `p` extension exists.
Date: Thu, 4 Feb 2021 15:48:44 -0800 [thread overview]
Message-ID: <CAFyWVabdtWZ-M3hQQsMxLc4fkNKTcm-QLRBveVnasJqyhgnbOg@mail.gmail.com> (raw)
In-Reply-To: <CALLt3ThJMf-nk4DJHOPHgGVNcGdeNZhKRY+Y1BpnA-9qUQLh4g@mail.gmail.com>
On Thu, Jan 21, 2021 at 10:49 PM Kito Cheng <kito.cheng@sifive.com> wrote:
> I think this patch is small enough to accept without FSF copyright
> assignment, and he is also on the way of the process, what do you
> think?
>
I see the copyright assignments on file at the FSF when I checked today.
Jim
prev parent reply other threads:[~2021-02-04 23:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 12:48 Xing GUO
2021-01-22 6:26 ` Kito Cheng
2021-01-22 6:44 ` Xing GUO
2021-01-22 6:48 ` Kito Cheng
2021-01-27 1:46 ` Xing GUO
2021-01-27 5:54 ` Xing GUO
2021-01-28 3:27 ` Kito Cheng
2021-01-31 18:38 ` Andreas Schwab
2021-02-01 0:59 ` Xing GUO
2021-02-01 8:58 ` Xing GUO
2021-02-01 9:36 ` Kito Cheng
2021-02-04 23:48 ` Jim Wilson [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=CAFyWVabdtWZ-M3hQQsMxLc4fkNKTcm-QLRBveVnasJqyhgnbOg@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=higuoxing@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.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).