From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org,
Par Olsson <par.olsson@windriver.com>
Subject: Re: [PATCH 1/2] Fix write endianness/size problem for fast tracepoint enabled flag
Date: Thu, 31 Mar 2016 12:58:00 -0000 [thread overview]
Message-ID: <86fuv6rehz.fsf@gmail.com> (raw)
In-Reply-To: <56FD0AE4.1050706@redhat.com> (Pedro Alves's message of "Thu, 31 Mar 2016 12:32:52 +0100")
Pedro Alves <palves@redhat.com> writes:
> Actually Wind River has a blanket copyright assignment:
>
> BINUTILS DEJAGNU GCC GDB Wind River Systems 1997-09-04
> Assigns past and future changes submitted to the FSF
> (gcc, g++, gdb, binutils, libg++, libstdc++, dejagnu,
> GNU C++ testsuite, GNU C testsuite).
Oh, right, I searched "windriver" (no space), and only find one record for
one person.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-03-31 12:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:17 Simon Marchi
2016-03-30 15:17 ` [PATCH 2/2] Add test for fast tracepoint enable/disable Simon Marchi
2016-03-31 10:58 ` Yao Qi
2016-03-31 18:01 ` Simon Marchi
2016-03-31 18:31 ` Simon Marchi
2016-04-01 13:36 ` Yao Qi
2016-04-01 14:42 ` Simon Marchi
2016-04-28 15:30 ` Simon Marchi
2016-04-28 16:03 ` Yao Qi
2016-04-28 16:57 ` Simon Marchi
2016-03-31 10:51 ` [PATCH 1/2] Fix write endianness/size problem for fast tracepoint enabled flag Yao Qi
2016-03-31 11:33 ` Pedro Alves
2016-03-31 12:58 ` Yao Qi [this message]
2016-03-31 17:45 ` Simon Marchi
2016-05-05 7:58 ` Yao Qi
2016-05-05 13:50 ` Simon Marchi
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=86fuv6rehz.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=par.olsson@windriver.com \
--cc=simon.marchi@ericsson.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