-
Notifications
You must be signed in to change notification settings - Fork 180
Provision the ability to apply the non upstream patches in any order #313
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
bd3916d
Provision the ability to apply the patches in any order
vivekrnv 0476dcb
Merge branch 'sonic-net:master' into non_upstream_order
vivekrnv 907f7a1
Make INCLUDE_EXTERNAL_PATCHES a mandatory parameter
vivekrnv 200edce
Merge branch 'master' into non_upstream_order
saiarcot895 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we had a discussion on the variable naming in #296, but since this is being renamed to
INCLUDE_EXTERNAL_PATCHES
, canEXTERNAL_KERNEL_PATCH_URL
fall under that, such that ifINCLUDE_EXTERNAL_PATCHES
is set ton
, then nothing happens, even ifEXTERNAL_KERNEL_PATCH_URL
is specified?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That means user has to provide both
EXTERNAL_KERNEL_PATCH_URL
&INCLUDE_EXTERNAL_PATCHES
, if they wish to use non-upstream patches from an external URL. Why have two control options?INCLUDE_EXTERNAL_PATCHES
is for locally saved non-up patches. atleast that's how i thought ofThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saiarcot895 Do you think it makes more sense to make
INCLUDE_EXTERNAL_PATCHES
a mandatory parameter.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thought was that because of the name
INCLUDE_EXTERNAL_PATCHES
, it is a parameter whether to include external patches at all, and thatEXTERNAL_KERNEL_PATCH_URL
is one source of those external patches.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, will update it then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Handled