-
Notifications
You must be signed in to change notification settings - Fork 281
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
[sonic-sairedis] Moved SAI submodule to SAI master #1506
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Abhishek Dosi <[email protected]>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@dgsudharsan for viz. @BYGX-wcr for viz. |
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.
Needed for srv6 support
/azp run Azure.sonic-sairedis |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-sairedis |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
please resolve conflicts |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Abhishek Dosi <[email protected]>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@kcudnik : can you please help check this build error ? |
code needs to be updated since you are moving SAI headers forward, which this change is not backward compatible, and there is no port_error_status in port_notifiation any more you need to remove that code, as well you can remove workaround on that notification in syncd |
What I did:
Moved SAI submodule to it's latest master in sonic-sairedis. Following SAI commits: