Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marcin Kościelnicki" <koriakin@0x04.net>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/8] gdb.trace: Fix write_inferior_data_ptr on 32-bit big-endian machines.
Date: Fri, 22 Jan 2016 14:06:00 -0000	[thread overview]
Message-ID: <56A2377A.5010203@0x04.net> (raw)
In-Reply-To: <56A2362D.2030109@redhat.com>

On 22/01/16 15:01, Pedro Alves wrote:
> OK with empty line after declaration.
>
> Thanks,
> Pedro Alves
>

Thanks, fixed & pushed.

Any comment about the bi-arch case?  Does that seem like something worth 
doing?

BTW, don't mind the 1/8 in subject, that was a git-format-patch 
accident.  The remaining 7 patches are not yet review-ready :)

Marcin Kościelnicki


  reply	other threads:[~2016-01-22 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 13:57 Marcin Kościelnicki
2016-01-22 14:01 ` Pedro Alves
2016-01-22 14:06   ` Marcin Kościelnicki [this message]
2016-01-22 14:10     ` Pedro Alves
2016-01-26 13:32 ` Ulrich Weigand
2016-01-26 13:45   ` Marcin Kościelnicki
2016-01-26 13:50     ` Ulrich Weigand

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=56A2377A.5010203@0x04.net \
    --to=koriakin@0x04.net \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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