public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] x32: Fast tracepoints support
Date: Tue, 23 Aug 2016 22:46:00 -0000	[thread overview]
Message-ID: <00b5aaec-a0f2-6f33-0c63-61820585f9ac@redhat.com> (raw)
In-Reply-To: <3758b413-66bc-4092-541c-b1f8c7b9f492@redhat.com>

On 08/19/2016 12:02 PM, Pedro Alves wrote:
> I almost forgot about this.  I'll push it all to master in
> a bit.
> 
> I think this is pretty safe to put in 7.12 as well though.
> Any thoughts?  Here's my analysis of the patches in the series:

I've pushed it to 7.12 now.

Thanks,
Pedro Alves

      reply	other threads:[~2016-08-23 22:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  1:01 Pedro Alves
2016-07-28  1:01 ` [PATCH 2/6] x32 Fast tracepoints: Customize jump pad address Pedro Alves
2016-07-28  1:01 ` [PATCH 1/6] x32 Fast tracepoints: IPA target descriptions Pedro Alves
2016-07-28  1:01 ` [PATCH 3/6] x32: Avoid unsigned long when installing fast tracepoint jump pads Pedro Alves
     [not found]   ` <CAMe9rOoDQGLd-uzdwewkBkwcQdKv+Y71q0L_DsFpWZSXHXnB6g@mail.gmail.com>
2016-07-28  8:51     ` Pedro Alves
2016-07-28  1:01 ` [PATCH 6/6] x32: Fix gdb.trace/mi-trace-frame-collected.exp Pedro Alves
2016-07-28  1:07 ` [PATCH 4/6] x32: gdbserver's agent bytecode JIT: fix "call" emission Pedro Alves
2016-07-28  1:09 ` [PATCH 5/6] x32: gdb: Fix 'call' insn relocation with qRelocInsn Pedro Alves
2016-07-28  7:23 ` [PATCH 0/6] x32: Fast tracepoints support Tedeschi, Walfred
2016-08-19 11:03 ` Pedro Alves
2016-08-23 22:46   ` Pedro Alves [this message]

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=00b5aaec-a0f2-6f33-0c63-61820585f9ac@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).