| commit | fef7894c1b56a29e47a0d11f3ef6915577235fec | [log] [tgz] |
|---|---|---|
| author | James E. Blair <jeblair@linux.vnet.ibm.com> | Fri Mar 11 16:28:56 2016 -0800 |
| committer | James E. Blair <jeblair@linux.vnet.ibm.com> | Mon Mar 21 19:58:27 2016 -0700 |
| tree | 457fe9ebe13570580bcdbf0f806556ed100bb7ce | |
| parent | 60af7f42d0cd24539c8d408a73a7bdbe6ce6e485 [diff] |
Remove scheduler parameter from connection registry The connection registry should not have to know about the scheduler, rather, the inverse is true. (NB, connections themselves still know about the scheduler, but that's okay, that happens after the connection registry is created.) Drivers should be able to access the global configuration when being created, so store that when the connection registry configures itself. Change-Id: Iea4b8fe3888b5eefd3df9ce385225b885f2caa0b