chrony: fix uci leapsecmode option - #30530
Merged
Merged
Conversation
Formality Check: Suggestions AvailableWe checked this pull request against the contribution guidelines. Here is what needs your attention:
|
openwrt-ai
reviewed
Sep 15, 2026
Fixes openwrt#30518. Signed-off-by: Miroslav Lichvar <mlichvar0@gmail.com>
mlichvar
force-pushed
the
chrony-uci-leapsecmode
branch
from
September 15, 2026 06:55
c88cfc2 to
b169e55
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
📦 Package Details
Maintainer: me
Description:
Fix name of the leapsecmode directive in the generated config from uci (#30518).
🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
No patches.