Version: 1
-Previous: d5f9c5aeb49673d47ba4d2b4b269b978e69e25ea
-Head: 23ffef06cf462c4c5ac4ec5880b96c8719b64774
+Previous: d428f8c6e7b0c829ea72e80d0eac7999510f3ef5
+Head: 8ec2a102c0faa99cd71c4227dea9fc2ad3bf90c0
Applied:
lazy-init: 23ffef06cf462c4c5ac4ec5880b96c8719b64774
+ rs-inline: 8ec2a102c0faa99cd71c4227dea9fc2ad3bf90c0
Unapplied:
old-af-ib: aaa0d9ca917c8c361a978e5a116963c2cceac5ba
old-seterr: 47eb0c419687c2690292c1910acae83a46e5388c
--- /dev/null
+Bottom: 09ed451c6b5c30d2dbe0bbedc3379ef8034dc899
+Top: 09ed451c6b5c30d2dbe0bbedc3379ef8034dc899
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2014-04-16 21:42:06 -0700
+
+rsocket: Check max inline data after creating QP
+
+The ipath provider will ignore the max_inline_size
+specified as input into ibv_create_qp and instead
+return the size that it supports (which is 0) on
+output. Check that the max_inline_size returned
+from ibv_create_qp is the size needed.
+
+
+---
+
+