RDKBDEV-2936: drop syscfg_init() as a public API #280
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
Reason for change: Initialisation is now handled automatically with the syscfg lib, so explicit calls to syscfg_init() are no longer required. Test Procedure: Sanity. Risks: None. Signed-off-by: Andre McCurdy <[email protected]> Signed-off-by: Pradeepta Das <[email protected]>
|
|
pradeeptakdas
changed the title
|
Internal ticket for tracking https://ccp.sys.comcast.net/browse/RDKCOM-5090 |
hpatel006c
approved these changes
Oct 18, 2024
sadhyama
reviewed
Oct 21, 2024
sadhyama
reviewed
Oct 21, 2024
sadhyama
approved these changes
Nov 4, 2024
|
Thanks @sadhyama for merging the changes |
sadhyama
pushed a commit
that referenced
this pull request
Jan 2, 2025
RDKBDEV-2936: drop syscfg_init() as a public API #280
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.
Reason for change:
Initialisation is now handled automatically with the syscfg lib, so explicit calls to syscfg_init() are no longer required.
Test Procedure: Sanity.
Risks: None.