From: Peter Hurley <peter@hurleysoftware.com>
To: Chris Purvis <Chris.Purvis@microfocus.com>,
Nic Percival <Nic.Percival@microfocus.com>,
"'Michael Matz'" <matz@suse.de>,
Kevin Fletcher <Kevin.Fletcher@microfocus.com>,
Paul Matthews <Paul.Matthews@microfocus.com>
Cc: "'NeilBrown'" <neilb@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 bisected regression] input_available_p() sometimes says 'no' when it should say 'yes'
Date: Tue, 05 May 2015 09:35:46 -0400 [thread overview]
Message-ID: <5548C732.7070209@hurleysoftware.com> (raw)
In-Reply-To: <2F7A2F2395CAC340B30E7E8A7D95533DB672BFF5@NWB-EXCHANGE4.microfocus.com>
On 05/05/2015 09:34 AM, Chris Purvis wrote:
> Peter,
>
> So is calling tcflush() a solution here?
>
> Regards,
> Chris
What is with the top-posting?
next prev parent reply other threads:[~2015-05-05 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 [this message]
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
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=5548C732.7070209@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=Chris.Purvis@microfocus.com \
--cc=Kevin.Fletcher@microfocus.com \
--cc=Nic.Percival@microfocus.com \
--cc=Paul.Matthews@microfocus.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox