From: Nelson Chu <nelson.chu@sifive.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Binutils <binutils@sourceware.org>,
gdb-patches@sourceware.org, Jim Wilson <jimw@sifive.com>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Kito Cheng <kito.cheng@sifive.com>,
Andrew Waterman <andrew@sifive.com>
Subject: Re: [PATCH v2 1/3] RISC-V: Enable elf attributes when default configure option isn't set.
Date: Thu, 15 Jul 2021 09:47:59 +0800 [thread overview]
Message-ID: <CAJYME4GMFsy+yGAW-o3SfO0XBxW4H2PQL6Ou_4s2OnE=f46uTQ@mail.gmail.com> (raw)
In-Reply-To: <mhng-76d89bbc-57b2-4b00-98a7-50edd650c593@palmerdabbelt-glaptop>
> Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
> Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
>
> I'm assuming you have gotten commit access working?
Yeah I have gotten the write access. Thanks, committed.
Nelson
next prev parent reply other threads:[~2021-07-15 1:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 7:28 [PATCH v2 0/3] RISC-V: The series to supporting mapping symbols Nelson Chu
2021-07-09 7:28 ` [PATCH v2 1/3] RISC-V: Enable elf attributes when default configure option isn't set Nelson Chu
2021-07-09 8:00 ` Kito Cheng
2021-07-13 7:07 ` Nelson Chu
2021-07-13 20:38 ` Palmer Dabbelt
2021-07-15 1:47 ` Nelson Chu [this message]
2022-02-25 13:57 ` Sebastian Huber
2021-07-09 7:28 ` [PATCH v2 2/3] RISC-V: PR27916, Support mapping symbols Nelson Chu
2021-07-15 15:16 ` Palmer Dabbelt
2021-07-16 2:58 ` Nelson Chu
2021-07-09 7:28 ` [PATCH v2 3/3] RISC-V: PR27916, Extend .insn directive to support hardcode encoding Nelson Chu
2021-07-09 8:01 ` Kito Cheng
2021-07-14 20:38 ` Palmer Dabbelt
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='CAJYME4GMFsy+yGAW-o3SfO0XBxW4H2PQL6Ou_4s2OnE=f46uTQ@mail.gmail.com' \
--to=nelson.chu@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jimw@sifive.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.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).