From: Rui Ueyama <rui314@gmail.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: Rui Ueyama <ruiu@bluewhale.systems>, binutils@sourceware.org
Subject: Re: [PATCH v2] RISC-V: emit R_RISCV_RELAX for the la pseudo instruction
Date: Tue, 12 Dec 2023 15:40:11 +0900 [thread overview]
Message-ID: <CACKH++ZjxYaE+-YFZjpmV26n2pFU1c7Rt08bZh4uQsPS-TUspw@mail.gmail.com> (raw)
In-Reply-To: <CAPpQWtCKCOFRAQX4h2O6tXEmBP8YqCk5q0i-9=YR30Uksn3Eqw@mail.gmail.com>
https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/397 has been merged.
I also completed the copyright assignment form.
Could you merge this patch?
On Thu, Sep 21, 2023 at 4:37 PM Nelson Chu <nelson@rivosinc.com> wrote:
>
> On Thu, Sep 21, 2023 at 1:32 PM Rui Ueyama <ruiu@bluewhale.systems> wrote:
>>
>> Thank you for reviewing! I'll let you know when you can merge this
>> patch (i.e. when my proposal is ratified.)
>
>
> Thanks :-)
>
>>
>> Meanwhile, do I need to fill in the copyright assignment form?
>
>
> Oops, I almost forgot this... Yes, it would be great and convenient if you have the assignment, I remember the new form was here,
> https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=tree;f=doc/Copyright
> You can fill one of them (probably, seem like all three look the same ), and then send it to assign@gnu.org.
>
> Thanks
> Nelson
next prev parent reply other threads:[~2023-12-12 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 7:01 [PATCH] " Rui Ueyama
2023-09-20 1:08 ` Nelson Chu
2023-09-20 8:31 ` [PATCH v2] " Rui Ueyama
2023-09-21 0:18 ` Nelson Chu
2023-09-21 5:32 ` Rui Ueyama
2023-09-21 7:37 ` Nelson Chu
2023-12-12 6:40 ` Rui Ueyama [this message]
2023-12-12 9:38 ` Nelson Chu
2023-12-12 9:25 ` Andreas Schwab
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=CACKH++ZjxYaE+-YFZjpmV26n2pFU1c7Rt08bZh4uQsPS-TUspw@mail.gmail.com \
--to=rui314@gmail.com \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.com \
--cc=ruiu@bluewhale.systems \
/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).