-
Notifications
You must be signed in to change notification settings - Fork 1.4k
manifest: Update zephyr revision with qdec fix #25326
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
manifest: Update zephyr revision with qdec fix #25326
Conversation
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, click the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 81f204d1c45bc8e48a0cf219ab375ee32409b89c more detailssdk-nrf:
zephyr:
Github labels
List of changed files detected by CI (2)Outputs:ToolchainVersion: 2b2cd9579a Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
Qdec kconfig description added. Signed-off-by: Karol Lasończyk <karol.lasonczyk@nordicsemi.no>
594138b to
81f204d
Compare
50096e2
into
nrfconnect:collab-nrfx-4.0
Memory footprint analysis revealed the following potential issuessample.bluetooth.fast_pair.locator_tag.release[nrf54l15dk/nrf54l05/cpuapp]: ROM size increased by 1024[B] in comparison to the main[21cff63] branch. - link (cc: @nrfconnect/ncs-si-bluebagel) Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-25326/2) |
Qdec kconfig description added.