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

[nrf noup] nrfconnect/telink: Adapt to zcbor 0.8.1 #381

Merged
merged 1 commit into from
Feb 20, 2024

Conversation

oyvindronningstad
Copy link
Contributor

@oyvindronningstad oyvindronningstad commented Jan 26, 2024

New parameter to ZCBOR_STATE_D()

@Damian-Nordic
Copy link
Contributor

@oyvindronningstad You don't have to update the upstream - it doesn't build anyway before updating NCS/Zephyr in the upstream.

@oyvindronningstad oyvindronningstad force-pushed the zcbor-0.8.1-nrf branch 2 times, most recently from ad1eec7 to 42aabda Compare January 29, 2024 09:20
@oyvindronningstad oyvindronningstad changed the title [nrf fromlist] nrfconnect/telink: Adapt to zcbor 0.8.1 [nrf noup] nrfconnect/telink: Adapt to zcbor 0.8.1 Jan 29, 2024
@oyvindronningstad oyvindronningstad marked this pull request as ready for review January 29, 2024 09:22
Copy link
Contributor

@kkasperczyk-no kkasperczyk-no left a comment

Choose a reason for hiding this comment

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

From what I see the new flag argument set to 0 has no impact on current functionality, so approving.

New parameter to ZCBOR_STATE_D()

Signed-off-by: Øyvind Rønningstad <oyvind.ronningstad@nordicsemi.no>
@jfischer-no jfischer-no merged commit a4d48b7 into nrfconnect:master Feb 20, 2024
8 checks passed
@oyvindronningstad oyvindronningstad deleted the zcbor-0.8.1-nrf branch February 21, 2024 10:28
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.

5 participants