public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: jbeulich@suse.com, Andrew Waterman <andrew@sifive.com>,
	 Jim Wilson <jim.wilson.gcc@gmail.com>,
	binutils@sourceware.org,  research_trasio@irq.a4lg.com,
	Fangrui Song <i@maskray.me>
Subject: Re: [PATCH] RISC-V: move various alias entries
Date: Mon, 28 Aug 2023 10:21:26 +0800	[thread overview]
Message-ID: <CAPpQWtDNoOea3ipFVoXmrHpmG6_35a6SnYt4_hk5jib+-yT8jw@mail.gmail.com> (raw)
In-Reply-To: <mhng-e168f3d3-2749-4aa5-9a7a-afd6f18d6273@palmer-ri-x1c9>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

On Fri, Aug 25, 2023 at 9:23 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:

> On Fri, 25 Aug 2023 06:01:07 PDT (-0700), jbeulich@suse.com wrote:
> > On 05.08.2023 03:40, Tsukasa OI wrote:
> >> On 2023/08/04 21:00, Jan Beulich via Binutils wrote:
> >> I support merging this patch without modification (or perhaps, with
> >> minor modification to the commit message?).
> >>
> >> Reviewed-by: Tsukasa OI <research_trasio@irq.a4lg.com>
> >
> > Arch maintainers - any view? I guess I'll wait another week or so and
> > commit if I don't hear anything to the contrary.
>
> Sorry for missing this.  It looks good to me, so
>
> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> but I remember talking about it at some point with Nelson.  It's the
> weekend already in Taiwain, so I'll try to remember to bug him on Monday
> if he doesn't see this.
>

Thanks, LGTM.

Nelson

      reply	other threads:[~2023-08-28  2:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 12:00 Jan Beulich
2023-08-05  1:40 ` Tsukasa OI
2023-08-25 13:01   ` Jan Beulich
2023-08-25 13:23     ` Palmer Dabbelt
2023-08-28  2:21       ` Nelson Chu [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=CAPpQWtDNoOea3ipFVoXmrHpmG6_35a6SnYt4_hk5jib+-yT8jw@mail.gmail.com \
    --to=nelson@rivosinc.com \
    --cc=andrew@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=i@maskray.me \
    --cc=jbeulich@suse.com \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=research_trasio@irq.a4lg.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).