public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
	Paul Donahue <pdonahue@ventanamicro.com>,
	 Tsukasa OI <research_trasio@irq.a4lg.com>,
	Vineet Gupta <vineetg@rivosinc.com>,
	binutils@sourceware.org
Subject: Re: [PATCH v1] RISC-V: Add mtinst and mtval2 CSRs (defined in priv-spec 1.12)
Date: Sat, 5 Feb 2022 00:27:43 +0100	[thread overview]
Message-ID: <CAAeLtUDCH4uVU02mvy0wkxgs5CiRMHjgsLFpaAVeDXmpFZAbNg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2202041818001.66221@arjuna.pair.com>

Thanks for the info. That is excellent news.
—Philipp.

On Sat 5. Feb 2022 at 00:23, Hans-Peter Nilsson <hp@bitrange.com> wrote:

> On Fri, 4 Feb 2022, Philipp Tomsich wrote:
>
> > Tsukasa,
> >
> > Last time I heard, you did not have copyright assignments in place.
> > Until this is resolved, I can not look at your patches to not lose the
> > ability to independently develop if needed (our community has been
> > burnt in this regard before).
>
> I'll again testify that they're in place:
> In copyright.list from 2022-02-01, I see an entry
> dated 2022-01-19 for BINUTILS Tsukasa OI "Assigns past and
> future changes".
>
> HTH.  Happy hacking.
>
> brgds, H-P
>

      parent reply	other threads:[~2022-02-04 23:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  0:13 Philipp Tomsich
2022-02-04  4:15 ` Tsukasa OI
2022-02-04  8:43   ` Philipp Tomsich
2022-02-04 23:23     ` Hans-Peter Nilsson
2022-02-04 23:25       ` Palmer Dabbelt
2022-02-04 23:27       ` Philipp Tomsich [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=CAAeLtUDCH4uVU02mvy0wkxgs5CiRMHjgsLFpaAVeDXmpFZAbNg@mail.gmail.com \
    --to=philipp.tomsich@vrull.eu \
    --cc=binutils@sourceware.org \
    --cc=hp@bitrange.com \
    --cc=kito.cheng@sifive.com \
    --cc=pdonahue@ventanamicro.com \
    --cc=research_trasio@irq.a4lg.com \
    --cc=vineetg@rivosinc.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).