public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
	 nd <nd@arm.com>
Subject: Re: [PATCH 6/6]: Remove xml files from gdbserver
Date: Mon, 22 Jan 2018 14:52:00 -0000	[thread overview]
Message-ID: <86po62djyr.fsf@gmail.com> (raw)
In-Reply-To: <A3F723A6-C407-4E89-B3BC-683B70287D79@arm.com> (Alan Hayward's	message of "Mon, 22 Jan 2018 13:23:54 +0000")

Alan Hayward <Alan.Hayward@arm.com> writes:

> Ok, happy to remove this patch from the series.

Part of this patch is still needed, as we can remove srv_xmlfiles for
the arches which can generate xml contents from target descriptions,
like x86, aarch64 and tic6x.

-- 
Yao (齐尧)

  reply	other threads:[~2018-01-22 14:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16  9:52 [PATCH 0/6] : Remove XML " Alan Hayward
2018-01-16  9:51 ` [PATCH 1/6] : Commonise various target-descriptions.c functions Alan Hayward
2018-01-16 14:18   ` Alan Hayward
2018-01-19 23:05   ` Yao Qi
2018-01-22 14:06     ` Alan Hayward
2018-01-22 15:47       ` Yao Qi
2018-01-16  9:52 ` [PATCH 2/6]: gdbserver use common tdesc functions Alan Hayward
2018-01-16  9:53 ` [PATCH 3/6] : Update dat files with arch and osabi Alan Hayward
2018-01-19 22:01   ` Yao Qi
2018-01-22 13:22     ` Alan Hayward
2018-01-22 15:28       ` Yao Qi
2018-01-16  9:55 ` [PATCH 6/6]: Remove xml files from gdbserver Alan Hayward
2018-01-19 22:11   ` Yao Qi
2018-01-22 13:23     ` Alan Hayward
2018-01-22 14:52       ` Yao Qi [this message]
2018-01-16  9:55 ` [PATCH 5/6] : Remove xml file references from target descriptions Alan Hayward
2018-01-16  9:55 ` [PATCH 4/6]: Create xml " 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=86po62djyr.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).