[action] [PR:14652] [Mellanox] Facilitate automatic integration of sdk kernel patches #15732
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.
Why I did it
Facilitate Automatic integration of sdk kernel patches into SONiC.
Inputs to the Script:
MLNX_SDK_VERSION
Eg:4.5.4206
MLNX_SDK_ISSU_VERSION
Eg:101
Note: If nothing is provided the one already present in the sdk.mk file is used
MLNX_SDK_SOURCE_BASE_URL:
Note: If nothing is provided the upstream sdk drivers url is used
CREATE_BRANCH: (y|n)
Creates a branch instead of a commit (optional, default: n)BRANCH_SONIC
: Only relevant when CREATE_BRANCH is y.Default: master
.Note: These should be provided through
SONIC_OVERRIDE_BUILD_VARS
parameterOutput:
MLNX_SDK_VERSION
Note: Script Doesn't commit anything to linux-kernel when there aren't any changes required..
How I did it
make integrate-mlnx-sdk
Changes made will be summarized under
sonic-buildimage/integrate-mlnx-sdk_user.out
file. Debugging and troubleshooting output is written tosonic-buildimage/integrate-mlnx-sdk.log
fileslog_files.zip
Limitations:
How to verify it
Build the Kernel and test
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)