From: Jeff Law <jeffreyalaw@gmail.com>
To: jinma <jinma@linux.alibaba.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/1] Fixed typo in RISCV
Date: Tue, 27 Dec 2022 10:31:46 -0700 [thread overview]
Message-ID: <42816bfe-91c2-05f9-5225-f69059d92157@gmail.com> (raw)
In-Reply-To: <9a484694-afb8-4100-a82c-d010c0007053.jinma@linux.alibaba.com>
On 12/22/22 23:06, jinma via Gcc-patches wrote:
> From 21904908689318ab81c630adc8cc7067e1a12488 Mon Sep 17 00:00:00 2001
> From: Jin Ma <jinma@linux.alibaba.com>
> Date: Fri, 23 Dec 2022 10:42:19 +0800
> Subject: [PATCH 1/1] Fixed typo
>
> gcc/ChangeLog:
>
> * common/config/riscv/riscv-common.cc:
Thanks. I've pushed this to the trunk.
jeff
prev parent reply other threads:[~2022-12-27 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 6:06 jinma
2022-12-27 17:31 ` Jeff Law [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=42816bfe-91c2-05f9-5225-f69059d92157@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jinma@linux.alibaba.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).