public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Faraz Shahbazker <fshahbazker@wavecomp.com>,
	Eli Zaretskii <eliz@gnu.org>, Mike Frysinger <vapier@gentoo.org>
Cc: cfu@wavecomp.com, gdb-patches@sourceware.org, macro@orcam.me.uk
Subject: Re: [EXTERNAL]Re: [PATCH 4/5] sim: mips: Add simulator support for mips32r6/mips64r6
Date: Sun, 27 Jun 2021 15:33:19 -0400	[thread overview]
Message-ID: <81dee879-8424-1e8b-020d-6f7152aff6ce@polymtl.ca> (raw)
In-Reply-To: <b9be41b3-9222-2ea0-2655-73b397513810@wavecomp.com>

On 2021-06-27 3:25 p.m., Faraz Shahbazker wrote:
> On 5/22/21 11:50 AM, Eli Zaretskii wrote:
>>> Date: Fri, 21 May 2021 21:46:33 -0400
>>> From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
>>> Cc: Chao-ying Fu <cfu@wavecomp.com>, gdb-patches@sourceware.org,
>>>   "Maciej W . Rozycki" <macro@orcam.me.uk>
>>>
>>> On 20 May 2021 13:15, Faraz Shahbazker wrote:
>>>> 2021-05-19  Ali Lown  <ali.lown@imgtec.com>
>>>>         Andrew Bennett  <andrew.bennett@imgtec.com>
>>>>         Dragan Mladjenovic  <dragan.mladjenovic@rt-rk.com>
>>>>         Faraz Shahbazker  <fshahbazker@wavecomp.com>
>>>
>>> i assume everyone has FSF papers in place ?
>>
>> Not that I could see, no.
> Can someone please clear this up for me? I was told by my manager in 2019 that papers were in place for Wave Computing, after which I posted a number of submissions without any questions. I assumed that the same would be good even now. The people who dealt with the FSF paperwork back then are no longer with Wave, so I can't easily verify at my end.
> 
> Thanks,
> Faraz

I do see an entry matching that in copyright.list, covering GDB (as well
as many other projets).  At line 44659 in the file, for those who have
access to it.  Sim is part of GDB for copyright-related things?

Simon


  reply	other threads:[~2021-06-27 19:33 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  7:45 [PATCH 0/5] Add support for MIPS32/64 revision 6 Faraz Shahbazker
2021-05-20  7:45 ` [PATCH 1/5] sim: Allow toggling of quiet NaN-bit semantics Faraz Shahbazker
2021-05-22  1:16   ` Mike Frysinger
2021-05-20  7:45 ` [PATCH 2/5] sim: Factor out NaN handling in floating point operations Faraz Shahbazker
2021-05-22  1:25   ` Mike Frysinger
2021-05-23  6:32     ` [EXTERNAL]Re: " Faraz Shahbazker
2021-05-24  1:26       ` Mike Frysinger
2021-05-20  7:45 ` [PATCH 3/5] sim: Add partial support for IEEE 754-2008 Faraz Shahbazker
2021-05-22  1:34   ` Mike Frysinger
2021-05-20  7:45 ` [PATCH 4/5] sim: mips: Add simulator support for mips32r6/mips64r6 Faraz Shahbazker
2021-05-22  1:46   ` Mike Frysinger
2021-05-22  6:20     ` Eli Zaretskii
2021-06-27 19:25       ` [EXTERNAL]Re: " Faraz Shahbazker
2021-06-27 19:33         ` Simon Marchi [this message]
2021-06-27 19:44           ` Eli Zaretskii
2021-06-27 20:24             ` Faraz Shahbazker
2021-06-28 12:17               ` Eli Zaretskii
2021-07-02 10:10                 ` Faraz Shahbazker
2021-12-24 18:42                   ` Mike Frysinger
2021-06-28  1:16           ` Mike Frysinger
2021-05-22  6:44     ` Faraz Shahbazker
2021-05-24 17:57     ` [PATCH v2 0/5] Add support for MIPS32/64 revision 6 Faraz Shahbazker
2021-05-24 17:57       ` [PATCH v2 1/5] sim: Allow toggling of quiet NaN-bit semantics Faraz Shahbazker
2021-05-24 17:57       ` [PATCH v2 2/5] sim: Factor out NaN handling in floating point operations Faraz Shahbazker
2021-05-24 17:58       ` [PATCH v2 3/5] sim: Add partial support for IEEE 754-2008 Faraz Shahbazker
2021-05-24 17:58       ` [PATCH v2 4/5] sim: mips: Add simulator support for mips32r6/mips64r6 Faraz Shahbazker
2021-05-24 17:58       ` [PATCH v2 5/5] gdb: mips: Add MIPSR6 support Faraz Shahbazker
2021-05-29  1:53         ` Simon Marchi
2021-06-27 19:10           ` [PATCH v3 " Faraz Shahbazker
2021-05-20  7:45 ` [PATCH " Faraz Shahbazker
2022-02-02 10:17 ` [PATCH v5 0/4] sim: Add support for MIPS32/64 revision 6 Dragan Mladjenovic
2022-02-02 10:17   ` [PATCH v5 1/4] sim: Allow toggling of quiet NaN-bit semantics Dragan Mladjenovic
2022-02-02 10:17   ` [PATCH v5 2/4] sim: Factor out NaN handling in floating point operations Dragan Mladjenovic
2022-02-02 10:17   ` [PATCH v5 3/4] sim: Add partial support for IEEE 754-2008 Dragan Mladjenovic
2022-02-02 10:17   ` [PATCH v5 4/4] sim: mips: Add simulator support for mips32r6/mips64r6 Dragan Mladjenovic
2022-12-25  0:26     ` Mike Frysinger
2022-12-27 19:35       ` Dragan Mladjenovic
2022-12-28  0:12         ` Mike Frysinger
2023-01-13 14:09           ` Dragan Mladjenovic
2022-02-04  5:48   ` [PATCH v5 0/4] sim: Add support for MIPS32/64 revision 6 Mike Frysinger
2022-02-04 12:29     ` Dragan Mladjenovic
2022-02-06 14:57       ` Joel Brobecker
2022-02-06 15:38         ` Dragan Mladjenovic
2022-02-06 16:28           ` Joel Brobecker
2022-02-06 18:49             ` Mike Frysinger
2022-02-07 11:48               ` Dragan Mladjenovic
2022-02-13 13:43                 ` Joel Brobecker
2022-02-14  0:04                   ` Mike Frysinger
2022-04-15  7:24                     ` Dragan Mladjenovic
2022-04-15  7:35                       ` Eli Zaretskii

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=81dee879-8424-1e8b-020d-6f7152aff6ce@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=cfu@wavecomp.com \
    --cc=eliz@gnu.org \
    --cc=fshahbazker@wavecomp.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=vapier@gentoo.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).