public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH v2 1/3] Remove args from target detach
Date: Fri, 19 Jan 2018 16:57:00 -0000	[thread overview]
Message-ID: <a136471d44b368c9de63768c1195763b@polymtl.ca> (raw)
In-Reply-To: <8fb3fa93-c59d-995a-b0fd-14f5c4248838@redhat.com>

On 2018-01-19 11:35, Pedro Alves wrote:
> On 01/19/2018 04:16 PM, Simon Marchi wrote:
>> From: Simon Marchi <simon.marchi@ericsson.com>
>> 
>> New in v2:
>> 
>> - Remove signo parameter from do_detach in procfs.c.
> 
> OK for the series.
> 
> Thanks,
> Pedro Alves

Thanks, pushed.

Simon

      reply	other threads:[~2018-01-19 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 16:16 Simon Marchi
2018-01-19 16:16 ` [PATCH v2 3/3] Make linux_nat_detach/thread_db_detach use the inferior parameter Simon Marchi
2018-01-28  6:32   ` [Regression] Segfault on native-extended-gdbserver + fork (was: Re: [PATCH v2 3/3] Make linux_nat_detach/thread_db_detach use the inferior parameter) Sergio Durigan Junior
2018-01-28 16:50     ` [Regression] Segfault on native-extended-gdbserver + fork Simon Marchi
2018-01-29 16:01       ` Pedro Alves
2018-01-29 16:25         ` Simon Marchi
2018-01-29 16:58           ` Pedro Alves
2018-01-29 17:04             ` Simon Marchi
2018-01-29 17:31               ` Pedro Alves
2018-01-29 17:36                 ` Pedro Alves
2018-01-29 17:24           ` Sergio Durigan Junior
2018-01-29 17:36             ` Sergio Durigan Junior
2018-01-29 17:47               ` Pedro Alves
2018-01-29 18:06                 ` Sergio Durigan Junior
2018-01-19 16:16 ` [PATCH v2 2/3] Pass inferior down to target_detach and to_detach Simon Marchi
2018-01-19 16:35 ` [PATCH v2 1/3] Remove args from target detach Pedro Alves
2018-01-19 16:57   ` Simon Marchi [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=a136471d44b368c9de63768c1195763b@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).