From: Mike Stump <mikestump@comcast.net>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] testsuite: btf: Fix btf-datasec-1.c for RISC-V
Date: Fri, 9 Sep 2022 21:10:30 -0700 [thread overview]
Message-ID: <393267CD-D19D-4E02-9B40-415FD0803E1D@comcast.net> (raw)
In-Reply-To: <CA+yXCZDWEtFXecOR9_LwTw0UpKAQsUoCd7BMyD+gqXr8ZBs52Q@mail.gmail.com>
On May 10, 2022, at 6:31 PM, Kito Cheng via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> LGTM, that's only added a new option for RISC-V and won't affect all
> other targets, so I assume I can approve that.
Yes. Usual and customary for ports.
prev parent reply other threads:[~2022-09-10 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 0:27 Palmer Dabbelt
2022-05-11 1:31 ` Kito Cheng
2022-05-13 16:53 ` Palmer Dabbelt
2022-09-10 4:10 ` Mike Stump [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=393267CD-D19D-4E02-9B40-415FD0803E1D@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.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).