From: Jonathan Yong <10walls@gmail.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c-c++-common/Wrestrict.c: fix some typos and enable for LLP64
Date: Sat, 2 Mar 2024 13:23:31 +0000 [thread overview]
Message-ID: <db421d28-1388-4f25-9768-6fdf995f9d96@gmail.com> (raw)
In-Reply-To: <a045b832-2fa1-4557-8b1e-4f6a234df66a@gmail.com>
On 2/15/24 14:08, Jonathan Yong wrote:
> Attached patch OK?
>
> Copy/pasted for review convenience.
Ping.
next prev parent reply other threads:[~2024-03-02 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 14:08 Jonathan Yong
2024-03-02 13:23 ` Jonathan Yong [this message]
2024-03-17 5:41 ` NightStrike
2024-03-17 17:38 ` Mike Stump
2024-03-18 23:37 ` Jonathan Yong
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=db421d28-1388-4f25-9768-6fdf995f9d96@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).