public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: ishitatsuyuki@gmail.com
Cc: gcc-patches@gcc.gnu.org, ishitatsuyuki@gmail.com
Subject: Re: [PATCH] Regenerate opt.urls
Date: Wed, 10 Apr 2024 06:46:04 -0700 (PDT)	[thread overview]
Message-ID: <mhng-8768f7fc-e3b9-4d01-b5a3-a790fce557af@palmer-ri-x1c9> (raw)
In-Reply-To: <20240409145724.9640-1-ishitatsuyuki@gmail.com>

On Tue, 09 Apr 2024 07:57:24 PDT (-0700), ishitatsuyuki@gmail.com wrote:
> Fixes: 97069657c4e ("RISC-V: Implement TLS Descriptors.")
>
> gcc/ChangeLog:
> 	* config/riscv/riscv.opt.urls: Regenerated.
> ---
>  gcc/config/riscv/riscv.opt.urls | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/gcc/config/riscv/riscv.opt.urls b/gcc/config/riscv/riscv.opt.urls
> index da31820e234..351f7f0dda2 100644
> --- a/gcc/config/riscv/riscv.opt.urls
> +++ b/gcc/config/riscv/riscv.opt.urls
> @@ -89,3 +89,5 @@ UrlSuffix(gcc/RISC-V-Options.html#index-minline-strncmp)
>  minline-strlen
>  UrlSuffix(gcc/RISC-V-Options.html#index-minline-strlen)
>
> +; skipping UrlSuffix for 'mtls-dialect=' due to finding no URLs
> +

Thanks.  I had another one over here 
<https://inbox.sourceware.org/gcc-patches/20240410000338.3926-1-palmer@rivosinc.com/>, 
but let's go with yours -- I think the actual contents are the same, but 
I didn't actually run the regenerate script.  So

Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
Acked-by: Palmer Dabbelt <palmer@rivosinc.com>

  reply	other threads:[~2024-04-10 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 14:57 Tatsuyuki Ishi
2024-04-10 13:46 ` Palmer Dabbelt [this message]
2024-04-12 19:25   ` Thomas Schwinge
2024-04-12 19:37     ` Palmer Dabbelt
2024-04-10  0:03 Palmer Dabbelt
2024-04-10  7:57 ` Andreas Schwab
2024-04-10 13:46   ` 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=mhng-8768f7fc-e3b9-4d01-b5a3-a790fce557af@palmer-ri-x1c9 \
    --to=palmer@dabbelt.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ishitatsuyuki@gmail.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).