-
Notifications
You must be signed in to change notification settings - Fork 35
Pull requests: openshift/linuxptp-daemon
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
OCPBUGS-69409: Ensure pin.ParentDevice length is ok in PhaseOffsetPin()
backport-risk-assessed
Indicates a PR to a release branch has been evaluated and considered safe to accept.
jira/valid-bug
Indicates that a referenced Jira bug is valid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
lgtm
Indicates that a PR is ready to be merged.
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
#514
opened Dec 16, 2025 by
javierpena
Loading…
OCPBUGS-66407: Backport clock class ticker
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
jira/severity-important
Referenced Jira bug's severity is important for the branch this PR is targeting.
jira/valid-bug
Indicates that a referenced Jira bug is valid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
lgtm
Indicates that a PR is ready to be merged.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#513
opened Dec 10, 2025 by
nocturnalastro
Loading…
OCPBUGS-66973: Ntpfailover backport 418
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
verified
Signifies that the PR passed pre-merge verification criteria
verified-later
#512
opened Dec 9, 2025 by
josephdrichard
Loading…
OCPBUGS-66971: Ntpfailover backport 419
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
verified
Signifies that the PR passed pre-merge verification criteria
verified-later
#511
opened Dec 8, 2025 by
josephdrichard
Loading…
ProTip!
Add no:assignee to see everything that’s not assigned.