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

advance dhcprelay to 4bf1868 #13205

Merged
merged 1 commit into from
Jan 2, 2023
Merged

advance dhcprelay to 4bf1868 #13205

merged 1 commit into from
Jan 2, 2023

Conversation

jcaiMR
Copy link
Contributor

@jcaiMR jcaiMR commented Dec 30, 2022

Why I did it

Advance dhcprelay submodule for master

  • 4bf1868 - (HEAD, origin/master, origin/HEAD, master) fix relay-reply dhcpv6 packet counter issue [jcaiMR]

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

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)

Copy link
Contributor

@StormLiangMS StormLiangMS left a comment

Choose a reason for hiding this comment

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

LGTM

@jcaiMR do we need to cherry-pick this to previous version?

@jcaiMR
Copy link
Contributor Author

jcaiMR commented Dec 30, 2022

LGTM

@jcaiMR do we need to cherry-pick this to previous version?

Yes, 202205 should be include. 202012 may need manual double commit.

@mssonicbld
Copy link
Collaborator

@jcaiMR PR conflicts with 202205 branch

@jcaiMR jcaiMR added the Request for 202111 Branch For PRs being requested for 202111 branch label Jan 13, 2023
@liushilongbuaa
Copy link
Contributor

It breaks PR into 202111 branch. Need to cherry-pick to 202111 branch.

@mssonicbld
Copy link
Collaborator

@jcaiMR PR conflicts with 202111 branch

@mssonicbld
Copy link
Collaborator

@jcaiMR PR conflicts with 202211 branch

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.

6 participants