Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Luis Machado <luis.machado@linaro.org>,
	"gdb-patches\\@sourceware.org"	<gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [review v4] [AArch64, SVE] Improve target description check for SVE in gdbserver
Date: Thu, 21 Nov 2019 08:23:00 -0000	[thread overview]
Message-ID: <024F5342-B699-4F3D-9CB9-92D544A25617@arm.com> (raw)
In-Reply-To: <c30acac0-f73f-c368-d980-94ece81e92e5@polymtl.ca>



> On 20 Nov 2019, at 16:51, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> 
> On 2019-11-20 11:34 a.m., Alan Hayward wrote:
>> (Gerrit appears not to be sending me account verification emails, so can’t review from there...)
> 
> There appears to be some problems with these emails, I don't know why
> at the moment.

Looks like they were working, but MS exchange quarantined them and didn’t let me know until this morning.

>  I've activated your account by hand.

Many thanks.

> 
> Simon


  parent reply	other threads:[~2019-11-21  8:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 14:03 [review] " Luis Machado (Code Review)
2019-11-19 14:05 ` [review v2] " Luis Machado (Code Review)
2019-11-19 14:23 ` Simon Marchi (Code Review)
2019-11-19 14:30 ` Luis Machado (Code Review)
2019-11-19 14:43 ` [review v3] " Luis Machado (Code Review)
2019-11-19 15:03 ` Simon Marchi (Code Review)
2019-11-19 15:14 ` [review v4] " Luis Machado (Code Review)
2019-11-20 16:34   ` Alan Hayward
2019-11-20 16:51     ` Luis Machado
     [not found]     ` <c30acac0-f73f-c368-d980-94ece81e92e5@polymtl.ca>
2019-11-21  8:23       ` Alan Hayward [this message]
2019-11-20 16:59 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-20 16:59 ` Sourceware to Gerrit sync (Code Review)

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=024F5342-B699-4F3D-9CB9-92D544A25617@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=nd@arm.com \
    --cc=simon.marchi@polymtl.ca \
    /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