From: Peter Hurley <peter@hurleysoftware.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
NeilBrown <neilb@suse.de>
Cc: Nic Percival <Nic.Percival@microfocus.com>,
Michael Matz <matz@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH man-pages] pty.7: clarify asynchronous nature of PTY IO.
Date: Wed, 06 May 2015 09:36:04 -0400 [thread overview]
Message-ID: <554A18C4.5040702@hurleysoftware.com> (raw)
In-Reply-To: <554A0861.8030806@gmail.com>
On 05/06/2015 08:26 AM, Michael Kerrisk (man-pages) wrote:
> On 05/06/2015 12:59 AM, NeilBrown wrote:
>> Peter: does this seem reasonable and accurate to you?
>
> I've got the patch sitting in a branch, in case Peter has suggestions for changes.
This is fine with me.
Regards,
Peter Hurley
next prev parent reply other threads:[~2015-05-06 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 6:20 [PATCH bisected regression] input_available_p() sometimes says 'no' when it should say 'yes' NeilBrown
2015-05-01 15:05 ` Peter Hurley
2015-05-04 12:24 ` Michael Matz
2015-05-04 16:32 ` Peter Hurley
2015-05-04 16:56 ` Michael Matz
2015-05-04 18:42 ` Peter Hurley
2015-05-05 8:20 ` Nic Percival
2015-05-05 11:18 ` Peter Hurley
2015-05-05 12:03 ` Nic Percival
2015-05-05 13:29 ` Peter Hurley
2015-05-05 13:34 ` Chris Purvis
2015-05-05 13:35 ` Peter Hurley
2015-05-05 13:37 ` Chris Purvis
[not found] ` <2F7A2F2395CAC340B30E7E8A7D95533DB672C022@NWB-EXCHANGE4.microfocus.com>
2015-05-05 17:39 ` Chris Purvis
2015-05-05 22:59 ` [PATCH man-pages] pty.7: clarify asynchronous nature of PTY IO NeilBrown
2015-05-06 12:26 ` Michael Kerrisk (man-pages)
2015-05-06 13:36 ` Peter Hurley [this message]
2015-05-06 16:12 ` Michael Kerrisk (man-pages)
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=554A18C4.5040702@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=Nic.Percival@microfocus.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.