Version: 1
-Previous: 3c97be238892c773804c25bc152c5780817f1e10
-Head: 5c5bd081e37a5788defb0ca0bc907b588524fa44
+Previous: c80ec19f01ef0fd3b2f6fd6ecec297b8c3cd75c9
+Head: bb8c7a321102a77a1d0b8e361f166fa00fc57c03
Applied:
+ nonblock: bb8c7a321102a77a1d0b8e361f166fa00fc57c03
Unapplied:
old-af-ib: aaa0d9ca917c8c361a978e5a116963c2cceac5ba
old-seterr: 47eb0c419687c2690292c1910acae83a46e5388c
--- /dev/null
+Bottom: bc6e27468c0f7e18f8977628c2581cff36914899
+Top: bc6e27468c0f7e18f8977628c2581cff36914899
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2015-02-05 21:17:03 -0800
+
+rsockets: Fix setting flags in rfctl
+
+The rfcntl() call to set rsocket flags merely OR's in
+the updated flags with the existing ones, rather than
+replacing them. Also, it does not handle setting an
+rsocket from nonblocking mode back to blocking mode.
+
+
+---
+
+