From: Jim Wilson <jim.wilson@linaro.org>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] aarch64 sim vector mul bug fix
Date: Thu, 05 Jan 2017 00:13:00 -0000 [thread overview]
Message-ID: <CABXYE2WbbBGnvouZre-O=XAoBLQVaOY3eX_y2Ko_JV8hoVneVQ@mail.gmail.com> (raw)
In-Reply-To: <e364cf96-b256-d756-9ac2-2c8338e0925c@redhat.com>
On Tue, Jan 3, 2017 at 6:35 AM, Nick Clifton <nickc@redhat.com> wrote:
> Also - would you be interested in becoming a maintainer for the AArch64 sim ?
> I certainly think that it would be good idea, and I think that Mike would
> probably be onboard with the idea too ...
Yes, I am willing to become a maintainer or co-maintainer for the
AArch64 sim. I'll have to start reading gdb-patches again to look for
aarch64 sim related messages, but I doubt that there are many relevant
ones.
Jim
next prev parent reply other threads:[~2017-01-05 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 22:24 Jim Wilson
2017-01-03 14:35 ` Nick Clifton
2017-01-05 0:13 ` Jim Wilson [this message]
[not found] ` <a68cfc77-a1b9-0163-c6a3-90a687b97e8b@redhat.com>
2017-02-14 18:24 ` Mike Frysinger
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='CABXYE2WbbBGnvouZre-O=XAoBLQVaOY3eX_y2Ko_JV8hoVneVQ@mail.gmail.com' \
--to=jim.wilson@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.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