Add few code exaples to documentation #194
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vpodzime
approved these changes
May 29, 2017
| @@ -375,6 +375,20 @@ GQuark bd_init_error_quark () | |||
| * | |||
There was a problem hiding this comment.
libblockdev in the commit message (all lower case)
libblockdev initialization and using the extra args (BDExtraArg) is quite complicated so add some code snippets to demonstrate usage of this functionality.
vojtechtrefny
force-pushed
the
master_docs-code-snippets
branch
from
1f8caee to
c852d72
Compare
tbzatek
added a commit
to tbzatek/libblockdev
that referenced
this pull request
May 2, 2024
Libatasmart' temperature_cb() as iterated via sk_disk_smart_get_temperature() goes through the table and only the last available value of four matched attributes is reported back to the caller. This is different from smartmontools which defines matching priority. While there are four attributes to be matched, the latter two are actually overrides from the standard set. This is where drivedb comes into play, however for the moment we don't have forward checking. Thus only match storaged-project#194 and storaged-project#190, which are typically safe.
tbzatek
added a commit
to tbzatek/libblockdev
that referenced
this pull request
May 27, 2024
Libatasmart' temperature_cb() as iterated via sk_disk_smart_get_temperature() goes through the table and only the last available value of four matched attributes is reported back to the caller. This is different from smartmontools which defines matching priority. While there are four attributes to be matched, the latter two are actually overrides from the standard set. This is where drivedb comes into play, however for the moment we don't have forward checking. Thus only match storaged-project#194 and storaged-project#190, which are typically safe.
tbzatek
added a commit
to tbzatek/libblockdev
that referenced
this pull request
May 27, 2024
Libatasmart' temperature_cb() as iterated via sk_disk_smart_get_temperature() goes through the table and only the last available value of four matched attributes is reported back to the caller. This is different from smartmontools which defines matching priority. While there are four attributes to be matched, the latter two are actually overrides from the standard set. This is where drivedb comes into play, however for the moment we don't have forward checking. Thus only match storaged-project#194 and storaged-project#190, which are typically safe.
tbzatek
added a commit
to tbzatek/libblockdev
that referenced
this pull request
May 27, 2024
Libatasmart' temperature_cb() as iterated via sk_disk_smart_get_temperature() goes through the table and only the last available value of four matched attributes is reported back to the caller. This is different from smartmontools which defines matching priority. While there are four attributes to be matched, the latter two are actually overrides from the standard set. This is where drivedb comes into play, however for the moment we don't have forward checking. Thus only match storaged-project#194 and storaged-project#190, which are typically safe.
vojtechtrefny
pushed a commit
that referenced
this pull request
Jul 24, 2024
Libatasmart' temperature_cb() as iterated via sk_disk_smart_get_temperature() goes through the table and only the last available value of four matched attributes is reported back to the caller. This is different from smartmontools which defines matching priority. While there are four attributes to be matched, the latter two are actually overrides from the standard set. This is where drivedb comes into play, however for the moment we don't have forward checking. Thus only match #194 and #190, which are typically safe.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Libblockdev initialization and using the extra args (BDExtraArg)
is quite complicated so add some code snippets to demonstrate
usage of this functionality.