Date: Wed, 17 Aug 2016 16:51:58 -0700 From: hiren panchasara <hiren@strugglingcoder.info> To: Peter Sewell <Peter.Sewell@cl.cam.ac.uk> Cc: "Jonathan T. Looney" <jtl@freebsd.org>, "freebsd-transport@freebsd.org" <freebsd-transport@freebsd.org>, Sam Kumar <samkumar99@gmail.com> Subject: Re: TCP_HAVERCVDFIN Message-ID: <20160817235158.GE68615@strugglingcoder.info> In-Reply-To: <CAHWkzRSvofzDoH-W6kkhr_JexjbWQkfvN5sX-Ws5NPM-_XhYDQ@mail.gmail.com> References: <CAGtMfeBWzGAmt2Kq9bejon54xiz%2BHBOEjho1z=NZe_0fqG5Z2g@mail.gmail.com> <D2B685A4.4F28E%jlooney@juniper.net> <CAHWkzRSvofzDoH-W6kkhr_JexjbWQkfvN5sX-Ws5NPM-_XhYDQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--cYtjc4pxslFTELvY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Resurrecting this thread. https://reviews.freebsd.org/D7475 I like this new behavior and it is being tested at NF and LLNW without any known problems. Any strong objection against it other than it _may_ break something? :-) I don't see us getting a conformance test suite anytime soon so I suggest we go ahead with this fix without any MFC and see how it goes? Cheers, Hiren --cYtjc4pxslFTELvY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJXtPicXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lXJgH/1LlScChWlQp+UzcUKTO/80N +Zosqk/SKmIJxgEZ8S6NpFKO5Ty6OGJSlSXlKd6uxUYvERsp1eX/9VA1WOb+9EVj XiGMdfpyz9ArDaRsPtpwUHMBbh+6JOspYAteKfczVY9FqN9LbUIVTYFEm/Z9Hu8l yLC2O6karcju3yJyDyzy+6cUdCop5UfVj3lJPS1SmHaxh+3QgrVqlArj7X6ow+2x y5AxxQankGNmew9MPS55FnpkOH4A0iL2/o8VLm20NPqu6YMiZuMvC6YccpT0Qc1A fiVCRfghkRnbUTcftwzWE4lbo+pIGQlNEw3vRbzmqIFjqucbOBCDs2YVsB/DT/s= =icaX -----END PGP SIGNATURE----- --cYtjc4pxslFTELvY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160817235158.GE68615>