public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Patrick O'Neill <patrick@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Cc: palmer@rivosinc.com, richard.guenther@gmail.com,
	kito.cheng@gmail.com, david.abd@gmail.com, schwab@linux-m68k.org,
	schwab@suse.de, gnu-toolchain@rivosinc.com
Subject: [committed gcc13 backport] RISCV: Inline subword atomic ops
Date: Tue, 16 May 2023 10:01:49 -0700	[thread overview]
Message-ID: <e626b650-ab3d-a948-9369-d8255ce46cc9@rivosinc.com> (raw)
In-Reply-To: <98967b49-12fd-012d-257c-eb0e6ba12941@gmail.com>

On 5/15/23 21:32, Jeff Law wrote:

>
>
> On 5/9/23 10:01, Patrick O'Neill wrote:
>> Ping.
> OK for backporting.  Sorry for the delay.
>
> jeff

Committed.

Thanks,
Patrick


      reply	other threads:[~2023-05-16 17:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 17:19 [gcc13 " Patrick O'Neill
2023-05-09 16:01 ` Patrick O'Neill
2023-05-16  4:32   ` Jeff Law
2023-05-16 17:01     ` Patrick O'Neill [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=e626b650-ab3d-a948-9369-d8255ce46cc9@rivosinc.com \
    --to=patrick@rivosinc.com \
    --cc=david.abd@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=richard.guenther@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=schwab@suse.de \
    /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).