Re: [PATCH 6/6] staging: fsl-mc: Changed version matching rules for MC object drivers

2015-04-08 Thread Alexander Graf
On 03/27/2015 10:01 PM, J. German Rivera wrote: Before this change, we were requiring a complete version match (major and minor version numbers) between MC objects and corresponding drivers, to allow MC objects to be bound to their drivers. We realized that a mismatch in minor version numbers

Re: [PATCH 6/6] staging: fsl-mc: Changed version matching rules for MC object drivers

2015-04-08 Thread Alexander Graf
On 03/27/2015 10:01 PM, J. German Rivera wrote: Before this change, we were requiring a complete version match (major and minor version numbers) between MC objects and corresponding drivers, to allow MC objects to be bound to their drivers. We realized that a mismatch in minor version numbers

[PATCH 6/6] staging: fsl-mc: Changed version matching rules for MC object drivers

2015-03-27 Thread J. German Rivera
Before this change, we were requiring a complete version match (major and minor version numbers) between MC objects and corresponding drivers, to allow MC objects to be bound to their drivers. We realized that a mismatch in minor version numbers should be tolerated, as long as the major version

[PATCH 6/6] staging: fsl-mc: Changed version matching rules for MC object drivers

2015-03-27 Thread J. German Rivera
Before this change, we were requiring a complete version match (major and minor version numbers) between MC objects and corresponding drivers, to allow MC objects to be bound to their drivers. We realized that a mismatch in minor version numbers should be tolerated, as long as the major version