Skip to content
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

[portsorch]: Use sai_serialize api to write to DB #331

Merged
merged 2 commits into from
Oct 4, 2017

Conversation

marian-pritsak
Copy link
Collaborator

Keep object IDs serializeable in database,
so that they can be reused later by client code

Keep object IDs serializeable in database,
so that they can be reused later by client code
@marian-pritsak
Copy link
Collaborator Author

Along with sonic-net/sonic-sairedis#234

@stcheng
Copy link
Contributor

stcheng commented Oct 3, 2017

could you resolve the conflicts?

@lguohan
Copy link
Contributor

lguohan commented Oct 4, 2017

can you resolve the conflict.

Copy link
Contributor

@lguohan lguohan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolve the conflict.

@marian-pritsak
Copy link
Collaborator Author

Done

@stcheng stcheng merged commit 5dd5e36 into master Oct 4, 2017
@stcheng stcheng deleted the marian-pritsak-patch-1 branch October 4, 2017 18:59
praveen-li pushed a commit to praveen-li/sonic-swss that referenced this pull request Aug 24, 2020
* msft_github/master:
  [portsorch]: Use sai_serialize api to write to DB (sonic-net#331)
  [portsorch]: Update comments (sonic-net#333)
  [switchorch]: Add support of ECMP and LAG hash seed attribute (sonic-net#324)
  [portsorch]: Add support of cable breakout feature (sonic-net#320)
oleksandrivantsiv pushed a commit to oleksandrivantsiv/sonic-swss that referenced this pull request Mar 1, 2023
Signed-off-by: Volodymyr Samotiy <volodymyrs@mellanox.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants