2016-12-09 19:48:12 +00:00
|
|
|
<!--- Provide a general summary of your changes in the Title above -->
|
|
|
|
|
|
|
|
### Description
|
|
|
|
<!--- Describe your changes in detail -->
|
|
|
|
|
|
|
|
### Motivation and Context
|
|
|
|
<!--- Why is this change required? What problem does it solve? -->
|
|
|
|
<!--- If it fixes an open issue, please link to the issue here. -->
|
|
|
|
|
|
|
|
### How Has This Been Tested?
|
|
|
|
<!--- Please describe in detail how you tested your changes. -->
|
|
|
|
<!--- Include details of your testing environment, and the tests you ran to -->
|
|
|
|
<!--- see how your change affects other areas of the code, etc. -->
|
|
|
|
<!--- If your change is a performance enhancement, please provide benchmarks here. -->
|
|
|
|
|
|
|
|
### Types of changes
|
|
|
|
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
|
|
|
|
- [ ] Bug fix (non-breaking change which fixes an issue)
|
|
|
|
- [ ] New feature (non-breaking change which adds functionality)
|
|
|
|
- [ ] Performance enhancement (non-breaking change which improves efficiency)
|
|
|
|
- [ ] Code cleanup (non-breaking change which makes code smaller or more readable)
|
|
|
|
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
|
|
|
|
|
|
|
|
### Checklist:
|
|
|
|
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
|
|
|
|
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
|
|
|
|
- [ ] My code follows the ZFS on Linux code style requirements.
|
|
|
|
- [ ] I have updated the documentation accordingly.
|
|
|
|
- [ ] I have read the **CONTRIBUTING** document.
|
|
|
|
- [ ] I have added tests to cover my changes.
|
|
|
|
- [ ] All new and existing tests passed.
|
2017-03-31 16:33:38 +00:00
|
|
|
- [ ] All commit messages are properly formatted and contain `Signed-off-by`.
|
2016-12-09 19:48:12 +00:00
|
|
|
- [ ] Change has been approved by a ZFS on Linux member.
|