Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiong Wang <jiong.wang@foss.arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: [AArch64][5/6] Implement gdbarch_core_read_description
Date: Wed, 09 Aug 2017 16:40:00 -0000	[thread overview]
Message-ID: <65de1747-f920-dae9-4e6c-00bdbc31cca5@foss.arm.com> (raw)
In-Reply-To: <86zib8ybgw.fsf@gmail.com>

On 09/08/17 17:03, Yao Qi wrote:

> Jiong Wang <jiong.wang@foss.arm.com> writes:
>
>> "auxv.h" to declare target_auxv_search and "elf/common.h" to define AT_HWCAP
>> (I miss read the buildbot error message as something like missing
>> "HWCAP_APIA"...)
>>
> Is it because the buildbot error message is too scary? :)

I was chuckle to myself after pushing the patch, the suddenly pop-up of buildbot
error message with "unfortunate" in the summary let me feel I got a sentence and
was nervously hurried to scroll down to the bottom, oh, my god, it's lifetime...


>
>> This patch was splitted from patch 6, I forget to move those two header files to
>> this patch.
>>
>> Attached patch fixed this and passed gdb cross build, OK for master?
> Yes, please.
>


  reply	other threads:[~2017-08-09 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c8484136-c4f2-cda2-6a0d-f8293b111cdd@foss.arm.com>
2017-08-09 12:17 ` [AArch64][3/6] DWARF unwinder support for signed return address Jiong Wang
2017-08-10 11:08   ` Pedro Alves
2017-08-10 13:35     ` Jiong Wang
2017-08-09 12:18 ` [AArch64][5/6] Implement gdbarch_core_read_description Jiong Wang
2017-08-09 14:22   ` Yao Qi
2017-08-09 14:57     ` Jiong Wang
2017-08-09 15:43       ` Jiong Wang
2017-08-09 16:04         ` Yao Qi
2017-08-09 16:40           ` Jiong Wang [this message]
2017-08-09 12:18 ` [AArch64][4/6] Prologue scan unwinder support for signed return address Jiong Wang

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=65de1747-f920-dae9-4e6c-00bdbc31cca5@foss.arm.com \
    --to=jiong.wang@foss.arm.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