Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix CRISv32 compilation
Date: Tue, 03 Sep 2013 12:03:00 -0000	[thread overview]
Message-ID: <5225D01E.9040701@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1309030857010.10770@lnxricardw.se.axis.com>

On 09/03/2013 08:45 AM, Ricard Wanderlof wrote:
> 
> On Mon, 2 Sep 2013, Pedro Alves wrote:
> 
>> On 08/30/2013 02:12 PM, Ricard Wanderlof wrote:
>>>
>>> 2013-08-30  Ricard Wanderlof  <ricardw@axis.com>
>>>
>>> gdbserver
>>>
>>>    	* linux-crisv32-low.c: Fix compilation errors.
>>
>> Write:
>>
>>    	* linux-crisv32-low.c (elf_gregset_t): Delete typedef.
>> 	(initialize_low_arch): Call init_registers_crisv32 rather than
>> 	init_register_crisv32.
>>
>> OK with that change.
> 
> Ok with me. Thanks for the update. Should I resubmit the patch ?

If there were no changes since the previous post, we just check
it in (and usually reply back saying so).  If the patch was approved
with changes, we commit, and reply back saying "this is what I
checked in", showing the final version.  Ultimately, what this means
is we always post final version of the patch to the mailing list,
exactly as it went in.

>> (I can't see how the typedef was breaking the build though)
> 
> With the typedef left in, I get

...

> when building gdbserver using the target compiler.

Thanks, that's the sort of info that's helpful to have the
in the patch rationale (which ideally ends up in the
commit log).

-- 
Pedro Alves


  parent reply	other threads:[~2013-09-03 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 13:13 Ricard Wanderlof
2013-09-02 17:29 ` Pedro Alves
     [not found]   ` <alpine.DEB.2.00.1309030857010.10770@lnxricardw.se.axis.com>
2013-09-03 12:03     ` Pedro Alves [this message]
2013-09-03 14:23       ` Ricard Wanderlof
2013-09-06  8:09   ` Ricard Wanderlof
2013-08-30 13:30 Ricard Wanderlof

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=5225D01E.9040701@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ricard.wanderlof@axis.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