From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: [PATCH 00/14] FIFO bug fixes and code simplifications
Date: Tue, 16 Apr 2019 11:20:00 -0000 [thread overview]
Message-ID: <20190416112011.GQ3599@calimero.vinschen.de> (raw)
In-Reply-To: <20190414191543.3218-1-kbrown@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
On Apr 14 19:15, Ken Brown wrote:
> Ken Brown (14):
> Cygwin: FIFO: rename client[] to fc_handler[]
> Cygwin: FIFO: hit_eof: add a call to fifo_client_lock
> Cygwin: FIFO: remember the type of the fhandler
> Cygwin: FIFO: fix a thinko in listen_client_thread
> Cygwin: FIFO: fix the error checking in raw_read
> Cygwin: check for STATUS_PENDING in fhandler_base::raw_read
> Cygwin: FIFO: code simplification: don't overload get_handle
> Cygwin: FIFO: fix fifo_client_handler::close
> Cygwin: FIFO: fix the use of the read_ready event
> Cygwin: FIFO: use a retry loop when opening a writer
> Cygwin: FIFO: fix clone
> Cygwin: FIFO: start the listen_client thread when duping a reader
> Cygwin: FIFO: improve raw_write
> Cygwin: FIFO: fix and simplify listen_client_thread
>
> winsup/cygwin/fhandler.cc | 14 +-
> winsup/cygwin/fhandler.h | 43 +--
> winsup/cygwin/fhandler_fifo.cc | 580 +++++++++++++++++----------------
> winsup/cygwin/select.cc | 4 +-
> 4 files changed, 342 insertions(+), 299 deletions(-)
>
> --
> 2.17.0
>
Pushed with v2 of patch 13. Developer snaps should be up shortly.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2019-04-16 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190414191543.3218-1-kbrown@cornell.edu>
2019-04-16 11:20 ` Corinna Vinschen [this message]
2019-04-16 11:23 ` Corinna Vinschen
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=20190416112011.GQ3599@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@cygwin.com \
--cc=cygwin-patches@cygwin.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).