From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Update comment in linux_nat_can_async_p
Date: Thu, 12 Jan 2017 16:05:00 -0000 [thread overview]
Message-ID: <3d26872a2cb94bc9e2bfc195c23b0f08@polymtl.ca> (raw)
In-Reply-To: <20170111082551.GI9518@E107787-LIN>
On 2017-01-11 03:25, Yao Qi wrote:
> On 17-01-10 15:30:26, Simon Marchi wrote:
>> I think this comment is outdated. Nowadays, linux-nat is always
>> async,
>> unless the user has explictly turned it off with
>> "maint set target-async off".
>>
>> gdb/ChangeLog:
>>
>> * linux-nat.c (linux_nat_can_async_p): Update comment.
>
> Looks good to me.
Thanks, I pushed it.
prev parent reply other threads:[~2017-01-12 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 20:31 Simon Marchi
2017-01-11 8:26 ` Yao Qi
2017-01-12 16:05 ` 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=3d26872a2cb94bc9e2bfc195c23b0f08@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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