Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH 3/7] Arm: Add read_description read funcs and use in GDB
Date: Wed, 10 Jul 2019 16:07:00 -0000	[thread overview]
Message-ID: <7511257b-e69d-4d77-c885-0ee16dad0a92@simark.ca> (raw)
In-Reply-To: <6071A4B3-3D8F-4C63-88FA-0DA2AB506F1C@arm.com>

On 2019-07-10 9:52 a.m., Alan Hayward wrote:
> Should probably read “called the once for each target description type”. But,
> removed due to comments below.

But shouldn't it be "called once" instead of "called the once", or it's really a valid
locution?  I have never heard that, and Googling "called the once" finds nothing of
interest.

Simon


  parent reply	other threads:[~2019-07-10 16:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05  9:46 [PATCH 0/7] Arm: Use feature target descriptions Alan Hayward
2019-07-05  9:45 ` [PATCH 3/7] Arm: Add read_description read funcs and use in GDB Alan Hayward
2019-07-10  3:45   ` Simon Marchi
2019-07-10 13:52     ` Alan Hayward
2019-07-10 14:26       ` Alan Hayward
2019-07-10 16:05         ` Simon Marchi
2019-07-10 16:07       ` Simon Marchi [this message]
2019-07-10 16:15         ` Alan Hayward
2019-07-05  9:45 ` [PATCH 4/7] Arm: Use feature target descriptions Alan Hayward
2019-07-05  9:46 ` [PATCH 6/7] Arm: Use read_description funcs in gdbserver Alan Hayward
2019-07-10  4:04   ` Simon Marchi
2019-07-10 15:44     ` Alan Hayward
2019-07-05  9:46 ` [PATCH 5/7] Arm: Add xml unit tests Alan Hayward
2019-07-05  9:46 ` [PATCH 2/7] Arm: Create feature files for Arm target descriptions Alan Hayward
2019-07-10  2:56   ` Simon Marchi
2019-07-10 13:22     ` Alan Hayward
2019-07-05  9:46 ` [PATCH 7/7] Arm: Remove unused feature files and tests Alan Hayward
2019-07-05  9:46 ` [PATCH 1/7] Arm: Minor style cleanups Alan Hayward

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=7511257b-e69d-4d77-c885-0ee16dad0a92@simark.ca \
    --to=simark@simark.ca \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.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