firehose: Allow bConfigDescrLock to be passed as 1 #80
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
During the introduction of UFS provisioning, the author left behind an additional safety measure of forcing the user to explicitly modify the source and recompile QDL in order to be able to lock the provisioning, to avoid users accidentally doing so. While it does reduce the risk of irreversable mistakes, it's not suitable when QDL is distributed as a binary - and the user already need to set bConfigDescrLock both in provided XML files and on command line. So, let's remove the safety net... Signed-off-by: Bjorn Andersson <[email protected]>
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.
During the introduction of UFS provisioning, the author left behind an additional safety measure of forcing the user to explicitly modify the source and recompile QDL in order to be able to lock the provisioning, to avoid users accidentally doing so.
While it does reduce the risk of irreversable mistakes, it's not suitable when QDL is distributed as a binary - and the user already need to set bConfigDescrLock both in provided XML files and on command line.
So, let's remove the safety net...