Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] [C++, AArch64] Fix warnings and errors
Date: Thu, 19 Nov 2015 13:43:00 -0000	[thread overview]
Message-ID: <564DD1E0.1080709@ericsson.com> (raw)
In-Reply-To: <1447938062-29624-1-git-send-email-yao.qi@linaro.org>

On 15-11-19 08:00 AM, Yao Qi wrote:
> This patch set fixes warnings and errors when I build GDB and GDBserver
> in C++ mode for native aarch64-linux.  There is still one error fixed
> by Simon's patch,
> 
>   [PATCH] Fix length calculation in aarch64_linux_set_debug_regs
>   https://sourceware.org/ml/gdb-patches/2015-11/msg00010.html
> 
> I think Simon's patch should go in too.  Each of them is obvious to
> me.  I'll push them in soon.
> 
> *** BLURB HERE ***
> 
> Yao Qi (4):
>   Cast void * to struct user_pt_regs *
>   Cast void * to user_fpsimd_state *.
>   Define enum out of the scope of struct
>   Change argument opcode type from enum aarch64_opcodes to uint32_t
> 
>  gdb/gdbserver/linux-aarch64-low.c | 24 ++++++++++++++----------
>  1 file changed, 14 insertions(+), 10 deletions(-)
> 

The series looks good to me.

Thanks!


  parent reply	other threads:[~2015-11-19 13:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 13:01 Yao Qi
2015-11-19 13:01 ` [PATCH 2/4] Cast void * to user_fpsimd_state * Yao Qi
2015-11-19 13:01 ` [PATCH 4/4] Change argument opcode type from enum aarch64_opcodes to uint32_t Yao Qi
2015-11-19 13:01 ` [PATCH 1/4] Cast void * to struct user_pt_regs * Yao Qi
2015-11-19 13:01 ` [PATCH 3/4] Define enum out of the scope of struct Yao Qi
2015-11-19 13:43 ` Simon Marchi [this message]
2015-11-19 14:03   ` [PATCH 0/4] [C++, AArch64] Fix warnings and errors 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=564DD1E0.1080709@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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