Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor libzfs_error_init newlines #9330

Merged
merged 1 commit into from Sep 18, 2019

Conversation

ghost
Copy link

@ghost ghost commented Sep 16, 2019

Motivation and Context

All other libzfs_error_* functions that return an error message do not include a trailing newline. Formatting is handled by the caller. This is also the convention outside of libzfs, for example strerror(3).

Description

Move the trailing newlines from the error message strings to the callers to more closely match the other error messages.

How Has This Been Tested?

Types of changes

  • 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)
  • Documentation (a change to man pages or other documentation)

Checklist:

Move the trailing newlines from the error message strings to the format
strings to more closely match the other error messages.

Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
@behlendorf behlendorf added the Status: Code Review Needed Ready for review and testing label Sep 16, 2019
@codecov
Copy link

codecov bot commented Sep 17, 2019

Codecov Report

Merging #9330 into master will increase coverage by 0.03%.
The diff coverage is 25%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #9330      +/-   ##
==========================================
+ Coverage   79.02%   79.05%   +0.03%     
==========================================
  Files         401      401              
  Lines      122469   122469              
==========================================
+ Hits        96777    96823      +46     
+ Misses      25692    25646      -46
Flag Coverage Δ
#kernel 79.77% <ø> (-0.02%) ⬇️
#user 66.67% <25%> (+0.16%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2a0d418...660e3d0. Read the comment docs.

@behlendorf behlendorf added Status: Accepted Ready to integrate (reviewed, tested) and removed Status: Code Review Needed Ready for review and testing labels Sep 18, 2019
@behlendorf behlendorf merged commit afc8f0a into openzfs:master Sep 18, 2019
@ghost ghost deleted the libzfs-error-newlines branch September 18, 2019 16:15
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Dec 24, 2019
Move the trailing newlines from the error message strings to the format
strings to more closely match the other error messages.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
Closes openzfs#9330
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Dec 27, 2019
Move the trailing newlines from the error message strings to the format
strings to more closely match the other error messages.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
Closes openzfs#9330
tonyhutter pushed a commit that referenced this pull request Jan 23, 2020
Move the trailing newlines from the error message strings to the format
strings to more closely match the other error messages.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
Closes #9330
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants