From: Yao Qi <qiyaoltc@gmail.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Philipp Rudo <prudo@linux.vnet.ibm.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] Move arch/tdesc.h to common/common-tdesc.h
Date: Thu, 22 Feb 2018 14:17:00 -0000 [thread overview]
Message-ID: <86lgflhzw1.fsf@gmail.com> (raw)
In-Reply-To: <CF1310CF-73E4-43FD-A418-DACABCC9A246@arm.com> (Alan Hayward's message of "Tue, 20 Feb 2018 11:56:18 +0000")
Alan Hayward <Alan.Hayward@arm.com> writes:
Hi Alan,
Patch is good to me.
> Tested by build for x86, ppc and aarch64, using both make 4.1 and make 3.81.
> Ran unittests for x86. Checked that my later patch series can apply on top.
>
> 2018-02-20 Alan Hayward <alan.hayward@arm.com>
>
> gdb/
> * arch/amd64.h: Use common/tdesc.h.
> * arch/i386.c: Likewise.
> * arch/i386.h: Likewise.
> * arch/tic6x.c: Likewise.
> * arch/tdesc.h: Move file from here...
> * common/tdesc.h: ...to here.
> * features/aarch64-core.c: Regenerate.
> * features/aarch64-fpu.c: Regenerate.
> * features/i386/32bit-avx.c: Regenerate.
> * features/i386/32bit-avx512.c: Regenerate.
> * features/i386/32bit-core.c: Regenerate.
> * features/i386/32bit-linux.c: Regenerate.
> * features/i386/32bit-mpx.c: Regenerate.
> * features/i386/32bit-pkeys.c: Regenerate.
> * features/i386/32bit-sse.c: Regenerate.
> * features/i386/64bit-avx.c: Regenerate.
> * features/i386/64bit-avx512.c: Regenerate.
> * features/i386/64bit-core.c: Regenerate.
> * features/i386/64bit-linux.c: Regenerate.
> * features/i386/64bit-mpx.c: Regenerate.
> * features/i386/64bit-pkeys.c: Regenerate.
> * features/i386/64bit-segments.c: Regenerate.
> * features/i386/64bit-sse.c: Regenerate.
> * features/i386/x32-core.c: Regenerate.
> * features/tic6x-c6xp.c: Regenerate.
> * features/tic6x-core.c: Regenerate.
> * features/tic6x-gp.c: Regenerate.
> * target-descriptions.c: Use common/tdesc.h.
> * target-descriptions.h: Likewise.
>
> gdbserver/
> * tdesc.c: Use common/tdesc.h.
> * tdesc.h: Likewise.
--
Yao (齐尧)
next prev parent reply other threads:[~2018-02-22 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 13:40 Alan Hayward
2018-02-01 11:19 ` Philipp Rudo
2018-02-01 13:19 ` Alan Hayward
2018-02-06 16:28 ` Yao Qi
2018-02-06 17:56 ` Philipp Rudo
2018-02-06 21:24 ` Yao Qi
2018-02-07 9:02 ` Philipp Rudo
2018-02-07 9:32 ` Yao Qi
2018-02-07 10:31 ` Alan Hayward
2018-02-20 11:56 ` Alan Hayward
2018-02-21 12:27 ` Philipp Rudo
2018-02-22 14:17 ` Yao Qi [this message]
2018-02-27 12:13 ` 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=86lgflhzw1.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=prudo@linux.vnet.ibm.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