From: Doug Evans <dje@google.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
gdb-patches <gdb-patches@sourceware.org>,
brian.murray@canonical.com, matthias.klose@canonical.com
Subject: Re: [PATCH] Fix PTRACE_GETREGSET failure for compat inferiors on arm64
Date: Fri, 02 Dec 2016 23:50:00 -0000 [thread overview]
Message-ID: <CADPb22T0bY3pZ9Q30ux4XE9y5tcHseTxFk6soNjVPs2Vwd4yYg@mail.gmail.com> (raw)
In-Reply-To: <20161202224952.panaxwmmrx4emord@localhost>
On Fri, Dec 2, 2016 at 2:49 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
> On 16-12-02 13:46:13, Kees Cook wrote:
>> gdb/ChangeLog:
>>
>> 2016-12-02 Kees Cook <keescook@google.com>
>
> You don't have FSF copyright assignment.
Hi.
Google has a blanket copyright assignment, so this is ok in that regard.
next prev parent reply other threads:[~2016-12-02 23:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 21:46 Kees Cook
2016-12-02 22:49 ` Yao Qi
2016-12-02 23:08 ` Kees Cook
2016-12-04 11:11 ` Yao Qi
2016-12-04 19:30 ` Kees Cook
2016-12-05 10:26 ` Yao Qi
2016-12-05 16:06 ` Kees Cook
2016-12-09 9:27 ` Yao Qi
2016-12-02 23:50 ` Doug Evans [this message]
2016-12-04 10:31 ` Yao Qi
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=CADPb22T0bY3pZ9Q30ux4XE9y5tcHseTxFk6soNjVPs2Vwd4yYg@mail.gmail.com \
--to=dje@google.com \
--cc=brian.murray@canonical.com \
--cc=gdb-patches@sourceware.org \
--cc=keescook@chromium.org \
--cc=matthias.klose@canonical.com \
--cc=qiyaoltc@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